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
Base idea: create-trigger in database, which gathers all tables with inserts for each test. In tear down calls a truncate only for those tables.
Advantages:
No need to recreate the database, connection_pools and connections
Easier integrating other services and their database access
Disadvantage: Not working with a standard prefilled database or rather will be more complicated
Some times to compare, all done on my T540-Laptop:
Running latest complete tests with creating new database for all backend system tests: 3255 passed, 243 skipped, 3 warnings in 2209.43s (0:36:49)
Running latest complete tests with truncate ALL TABLE NAMES RESTART IDENTITY CASCADE for all backend system tests: 3255 passed, 243 skipped in 3898.03s (1:04:58)
Ready state on 26.08.2024 with truncate only on triggered tables: 3565 passed, 267 skipped, 1 warning in 975.12s (0:16:15)
The text was updated successfully, but these errors were encountered:
Base idea: create-trigger in database, which gathers all tables with inserts for each test. In tear down calls a truncate only for those tables.
Advantages:
Disadvantage: Not working with a standard prefilled database or rather will be more complicated
Some times to compare, all done on my T540-Laptop:
Running latest complete tests with creating new database for all backend system tests: 3255 passed, 243 skipped, 3 warnings in 2209.43s (0:36:49)
Running latest complete tests with truncate ALL TABLE NAMES RESTART IDENTITY CASCADE for all backend system tests: 3255 passed, 243 skipped in 3898.03s (1:04:58)
Ready state on 26.08.2024 with truncate only on triggered tables: 3565 passed, 267 skipped, 1 warning in 975.12s (0:16:15)
The text was updated successfully, but these errors were encountered: