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: docs/UnitTests/README.md
+9-17Lines changed: 9 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,18 +122,10 @@ The basic idea behind those is that every test gets its own database copy. This
122
122
123
123
A test base for your database tests is available called `DatabaseUnitTest`. Type parameters are the test fixture optionally the `DbContext`. Example base classes in your test lib:
The `DatabaseUnitTest` provides the methods `Query` and `QueryAsync`. This is basically shortcut to resolving the `DbContext` and using it. So instead of writing
@@ -323,8 +315,8 @@ To solve this, you can either throttle your tests, or increase the max. connecti
323
315
To increase the max. connections of your postgres test instance, just pass the parameter max_connections. Example for a docker compose file:
324
316
```yaml
325
317
postgres_test:
326
-
image: postgres:14
327
-
command: -c max_connections=300
318
+
image: postgres:17
319
+
command: -c max_connections=500
328
320
ports:
329
321
- "5433:5432"
330
322
volumes:
@@ -339,15 +331,15 @@ postgres_test:
339
331
Alternatively, if you want to throttle your tests instead, you can to this easily with a semaphore in your test base:
0 commit comments