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
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,13 +9,13 @@ Code Yellow backend framework for SPA webapps with REST-like API.
9
9
10
10
## Running the tests
11
11
12
-
Run with docker `docker compose run binder ./setup.py test` (but you may need to run `docker compose build db binder` first)
13
-
- Access the test database directly by with `docker compose run db psql -h db -U postgres`.
12
+
-Run with `./test`
13
+
- Access the test database directly by with `docker compose run --rm db psql -h db -U postgres`.
14
14
- It may be possible to recreate the test database (for example when you added/changed models). One way of achieving this is to just remove all the docker images that were build `docker compose rm`. The database will be created during the setup in `tests/__init__.py`.
15
15
16
16
The tests are set up in such a way that there is no need to keep migration files. The setup procedure in `tests/__init__.py` handles the preparation of the database by directly calling some build-in Django commands.
17
17
18
-
To only run a selection of the tests, use the `-s` flag like `./setup.py test -s tests.test_some_specific_test`.
18
+
To only run a selection of the tests, use the `-k` flag like `./test -k tests.test_some_specific_test`.
0 commit comments