Lobo_Corp/ToBePlayed-Auth
Public Access
3
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test: one test container and one context per test kind
Build, Test & Push Auth Service / quality-check (push) Successful in 43s
Details
Build, Test & Push Auth Service / docker (push) Successful in 1m29s
Details

Browse Source
This commit is contained in:
lobo committed 2026-09-30 13:41:57 +02:00
1 parent 1f94c87a20
commit 3336181cdb
20 files changed
+65 -130
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

readme.md
+3 -1
View File
@@ -153,7 +153,9 @@ use each other.
ArchUnit enforces these rules in `src/test/java/auth_service/architecture/ArchitectureTest.java`, so a layer
violation fails the build. It also keeps the modules independent of each other and free of cycles. Test base
classes (`AbstractUnitTest`, `AbstractWebMvcTest`, `AbstractPersistenceTest`, `AbstractIntegrationTest`) live in
`auth_service.shared.test`; all integration tests share one PostgreSQL container.
`auth_service.shared.test`. Integration and persistence tests share one PostgreSQL container (`TestPostgres`), and
the base classes carry every annotation, so each kind starts one Spring context. A test with its own annotations
starts another one.
### Login flow