You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 19, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: docs/contributing.md
+34-2Lines changed: 34 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,8 +66,40 @@ run all of those with lint script
66
66
2. The simples one is for sqlite alone: `sqlite:///test.db`
67
67
68
68
3. Prepare tests (all backends)
69
-
1. In order to run all backends you need a docker instalation on your system [from here](https://docs.docker.com/get-docker/)
70
-
2. You need to set-up `TEST_IN_DOCKER` env variable (to any non-null value `YES` or `1`)
69
+
1. In order to run all backends you need either a docker installation on your system or all supported backends servers installed on your local machine.
70
+
2. A sample docker configuration that reflects the CI/CD workflow of databases might be:
71
+
72
+
```dockerfile
73
+
version: '2.1'
74
+
services:
75
+
postgres:
76
+
image: postgres:10.8
77
+
environment:
78
+
POSTGRES_USER: username
79
+
POSTGRES_PASSWORD: password
80
+
POSTGRES_DB: testsuite
81
+
ports:
82
+
- 5432:5432
83
+
84
+
mysql:
85
+
image: mysql:5.7
86
+
environment:
87
+
MYSQL_USER: username
88
+
MYSQL_PASSWORD: password
89
+
MYSQL_ROOT_PASSWORD: password
90
+
MYSQL_DATABASE: testsuite
91
+
ports:
92
+
- 3306:3306
93
+
```
94
+
3. To test all backends, the test urls need to consist of all possible drivers too, so a sample might look like following:
0 commit comments