* MP-8 OTHER Implementiere JWT-Authentifizierungs-Filter im Gateway * Fix(ci): Update upload-artifact action to v4 * Fix(ci): Add start command for Keycloak and failure logs * Fix(ci): Remove invalid 'command' property from Keycloak service * Fix(ci): Use KC_DEV_MODE env var to start Keycloak * Fix(ci): Keycloak service was removed from GitHub Actions services and replaced with a manual docker run step that starts Keycloak with the start-dev command. * dev(ci): vereinheitliche Keycloak auf 26.4.2; aktiviere Health im CI (MP-8) * Fix(ci): Stabilize Keycloak startup in integration tests via matrix - Add `dev-file` Keycloak variant to matrix for stability fallback. - Improve wait logic and health checks for Keycloak and Postgres. - Unify Keycloak version to 26.4.2 across codebase. - Add log dumps on failure. * Fix(ci): Die betroffene Datei docs/Visionen-Ideen/Infrastruktur-Strategie_DSGVO-Konformität.md endet aktuell mit genau einer leeren Zeile (Zeile 87). Das entspricht der Regel MD047 („Files should end with a single newline character“). Damit ist deine Korrektur korrekt. * Fix(ci): Repository-wide auto-fix for Markdown files was implemented with a GitHub Actions workflow and a local helper script. EditorConfig and markdownlint ignore files were added to ensure consistent formatting. Instructions for using the auto-fix both via GitHub Actions and locally were provided. * fix(gradle): build.gradle.kts jsBrowser testTask disabled * fix(gradle): build.gradle.kts jsBrowser testTask disabled * Fix(ci): Stabilize integration tests with Keycloak matrix build (MP-8) Introduces a matrix strategy (`keycloak_db: [postgres, dev-file]`) in the integration-tests workflow to mitigate flaky Keycloak starts when using the Postgres service container. - Adds a `dev-file` Keycloak variant for stability fallback. - Improves wait logic and health checks for Keycloak/Postgres. - Unifies Keycloak version to 26.4.2 across codebase (Dockerfile, Compose, ADR, README, tests). - Adds log dumps on failure in CI. - Ensures `KC_HEALTH_ENABLED=true` is set. - Updates related documentation (README, Schlachtplan). - Includes broader Docker SSoT cleanup (versions.toml as source, script updates, env file cleanup, validator hardening). This resolves recurring CI failures related to Keycloak startup and ensures required checks for PRs (#15) are reliable, while also improving overall Docker build consistency. * feat(docs, ci): Implement YouTrack SSoT strategy with Dokka sync (MP-8) - Add Dokka multi-module Gradle configuration and KDoc style guide. - Add GitHub Actions workflow (docs-kdoc-sync.yml) and Python script (youtrack-sync-kb.py) to sync Dokka GFM output to YouTrack KB. - Extend front-matter schema (bc, doc_type) and update relevant pages/stubs. - Adapt CI scripts (validate-frontmatter, check-docs-drift, ci-docs link ignore). - Update README.md to reference YouTrack KB. * feat(docs, ci): Implement YouTrack SSoT strategy with Dokka sync (MP-8) - Add Dokka multi-module Gradle configuration and KDoc style guide. - Add GitHub Actions workflow (docs-kdoc-sync.yml) and Python script (youtrack-sync-kb.py) to sync Dokka GFM output to YouTrack KB. - Extend front-matter schema (bc, doc_type) and update relevant pages/stubs. - Adapt CI scripts (validate-frontmatter, check-docs-drift, ci-docs link ignore). - Update README.md to reference YouTrack KB. * Fix(ci): Replace OpenAPI validator with Spectral Replaces the deprecated 'char0n/swagger-editor-validate' action, which failed due to sandbox issues in GitHub Actions, with the modern '@stoplight/spectral-cli'. This ensures robust OpenAPI specification validation without requiring a headless browser environment. The 'generate-api-docs' job now depends on the successful completion of the Spectral validation. Part of resolving CI failures for PR #15 (MP-8). * Fix(ci): Specify spectral:oas ruleset for OpenAPI validation (MP-8) * Fix(ci): Remove explicit ruleset argument for Spectral validation (MP-8) * Fix(ci): Added a .spectral.yaml file to fix Spectral linting errors. Corrected markdown lint issues in two documentation files. Updated README.md with a new guidelines section to fix link validation errors. * Fix(ci): Markdownlint errors were fixed by adding required blank lines. The Guidelines Validation error was resolved by updating the README.md link. The API Documentation Generator workflow was stabilized by updating paths, tasks, and validation steps. * Fix(ci): Alle vier fehlerhaften GitHub-Action-Prüfungen wurden behoben. Fehler in der OpenAPI-Spezifikation, Probleme mit der Markdown-Linting-Analyse und Validierungsfehler bei Querverweisen wurden korrigiert. Die README.md enthält nun alle erforderlichen Links zu den Richtlinien. * Fix(ci): Markdown linting errors in docs/api/README.md were fixed by specifying languages in fenced code blocks. OpenAPI specification errors in documentation.yaml were resolved by correcting example property types to strings. Cross-reference validation errors in README.md were fixed by adding the missing link to project-standards/coding-standards.md. * Fix(ci): Duplicate heading errors in docs/api/members-api.md were fixed. Cross-reference validation errors for docker-architecture.md were resolved. All originally reported issues passed validation successfully. * Fix(ci): The markdown heading levels in docs/api/members-api.md were corrected from h5 to h4 to fix linting errors. The missing cross-reference link from technology-guides/docker/docker-development.md to docker-overview.md was added. These fixes resolved the original validation and linting errors causing the process to fail. * Fix(ci): Duplicate heading warnings in docs/api/members-api.md were resolved. Cross-reference validation for docker-development.md to docker-architecture.md was fixed. A new unrelated warning about docker-production.md was identified but not addressed. * refactor(ci,docs): Simplify CI pipeline and migrate docs to YouTrack SSoT BREAKING CHANGE: Documentation structure radically simplified - Consolidate 9 GitHub Actions workflows into 1 main pipeline (ci-main.yml) - Remove redundant workflows: ci-docs, markdownlint-autofix, guidelines-validation, api-docs - Delete documentation migrated to YouTrack: api/, BCs/, Visionen-Ideen/, reference/, now/, overview/ - Keep only ADRs, C4 diagrams, and essential dev guides in repo - Update README.md with YouTrack KB links - Create new docs/README.md as documentation gateway - Relax markdown-lint config for pragmatic developer experience Kept workflows: - ssot-guard.yml (Docker SSoT validation) - docs-kdoc-sync.yml (KDoc → YouTrack sync) - integration-tests.yml (Integration tests) - deploy-proxmox.yml (Deployment) - youtrack-sync.yml (YouTrack integration) Related: MP-DOCS-001 * refactor(ci,docs): Simplify CI pipeline and migrate docs to YouTrack SSoT BREAKING CHANGE: Documentation structure radically simplified - Consolidate 9 GitHub Actions workflows into 1 main pipeline (ci-main.yml) - Remove redundant workflows: ci-docs, markdownlint-autofix, guidelines-validation, api-docs - Delete documentation migrated to YouTrack: api/, BCs/, Visionen-Ideen/, reference/, now/, overview/ - Keep only ADRs, C4 diagrams, and essential dev guides in repo - Update README.md with YouTrack KB links - Create new docs/README.md as documentation gateway - Relax markdown-lint config for pragmatic developer experience Kept workflows: - ssot-guard.yml (Docker SSoT validation) - docs-kdoc-sync.yml (KDoc → YouTrack sync) - integration-tests.yml (Integration tests) - deploy-proxmox.yml (Deployment) - youtrack-sync.yml (YouTrack integration) Related: MP-DOCS-001 * refactor(ci,docs): README.md und einige andere Dokumentationen überarbeitet. ports-and-urls.md hinzugefügt. Related: MP-DOCS-001 * refactor(ci,docs): Die Markdownlint-Fehler in README.md und docs/README.md wurden behoben, indem die Überschriftenebenen angepasst, überflüssige Satzzeichen am Ende entfernt und die notwendigen Leerzeilen um Überschriften, Listen, Tabellen und Codeblöcke eingefügt wurden. Das problematische Leerzeichen am Ende in docs/README.md wurde ebenfalls entfernt. Die Dateien entsprechen nun den vorgegebenen Markdownlint-Regeln und sollten die CI-Validierung bestehen. Related: MP-DOCS-001 * refactor(ci,docs): Docker guideline cross-references were fixed and normalized to lowercase labels. Validation scripts confirmed zero cross-reference warnings and consistent metadata. Documentation was updated with a changelog and enhanced README navigation. Related: MP-DOCS-001 * refactor(ci,docs): Docker guideline cross-references were fixed and normalized to lowercase labels. Validation scripts confirmed zero cross-reference warnings and consistent metadata. Documentation was updated with a changelog and enhanced README navigation. Related: MP-DOCS-001 * refactor(ci,docs): Dead links in docs/architecture/adr were fixed by updating URLs to stable sources and adding an ignore pattern for a placeholder link. Specific ADR files had their broken links replaced with valid ones. The markdown-link-check GitHub Action is expected to pass with zero dead links now. Related: MP-DOCS-001 * refactor(ci,docs): Links in ADR checked Related: MP-DOCS-001 * refactor(ci,docs): Links in ADR checked Related: MP-DOCS-001 * refactor(ci,docs): Markdown Regeln ausgebessert Related: MP-DOCS-001 * refactor(ci,docs): Markdown Regeln ausgebessert Related: MP-DOCS-001 * refactor(ci,docs): Markdown Regeln ausgebessert Related: MP-DOCS-001 * Chore: Rerun CI checks with updated branch protection rules
11 KiB
Testing Standards und Qualitätssicherung
guideline_type: "project-standards" scope: "testing-standards" audience: ["developers", "ai-assistants"] last_updated: "2025-09-15" dependencies: ["master-guideline.md", "coding-standards.md"] related_files: ["build.gradle.kts", "src/test/**", "testcontainers.properties"] ai_context: "Testing strategies, test pyramid, tools, coverage requirements, and debugging practices"
🧪 Testing Standards
Tests sind ein integraler Bestandteil jedes Features und müssen einen hohen Standard erfüllen.
🤖 AI-Assistant Hinweis: Testing-Prinzipien für das Meldestelle-Projekt:
- Test-Pyramide: 80 %+ Unit-Tests, Integrationstests für externe Systeme
- Testcontainers: Goldstandard für Infrastruktur-Tests
- Debug-Logs: Präfix
[DEBUG_LOG]für Test-Ausgaben- Result-Pattern: Tests müssen auch Error-Handling validieren
Test-Pyramide & Werkzeuge
Unit-Tests (80 %+ Abdeckung)
Für Domänen- und Anwendungslogik (JUnit 5, MockK).
class MemberServiceTest {
private val memberRepository = mockk<MemberRepository>()
private val eventPublisher = mockk<EventPublisher>()
private val memberService = MemberService(memberRepository, eventPublisher)
@Test
fun `should return Success when member is created successfully`() {
// Given
val command = CreateMemberCommand(
memberId = MemberId.generate(),
name = "Max Mustermann",
email = "max@example.com"
)
every { memberRepository.save(any()) } returns Result.Success(Unit)
every { eventPublisher.publish(any()) } returns Result.Success(Unit)
// When
val result = memberService.createMember(command)
// Then
assertThat(result).isInstanceOf<Result.Success<Unit>>()
verify { memberRepository.save(any()) }
verify { eventPublisher.publish(ofType<MemberCreatedEvent>()) }
}
@Test
fun `should return Failure when repository save fails`() {
// Given
val command = CreateMemberCommand(
memberId = MemberId.generate(),
name = "Max Mustermann",
email = "max@example.com"
)
every { memberRepository.save(any()) } returns Result.Failure(RepositoryError.DATABASE_ERROR)
// When
val result = memberService.createMember(command)
// Then
assertThat(result).isInstanceOf<Result.Failure<RepositoryError>>()
verify { memberRepository.save(any()) }
verify(exactly = 0) { eventPublisher.publish(any()) }
}
}
Integrationstests
Decken alle Repository-Implementierungen und externen Integrationen ab.
@Testcontainers
class MemberRepositoryIntegrationTest {
@Container
private val postgresContainer = PostgreSQLContainer("postgres:16-alpine")
.withDatabaseName("testdb")
.withUsername("test")
.withPassword("test")
private lateinit var memberRepository: MemberRepository
@BeforeEach
fun setup() {
val dataSource = HikariDataSource().apply {
jdbcUrl = postgresContainer.jdbcUrl
username = postgresContainer.username
password = postgresContainer.password
}
// Run migrations
Flyway.configure()
.dataSource(dataSource)
.locations("db/migration")
.load()
.migrate()
memberRepository = PostgresMemberRepository(dataSource)
}
@Test
fun `should save and retrieve member successfully`() {
// Given
val member = Member(
id = MemberId.generate(),
name = "Integration Test Member",
email = "integration@test.com"
)
// When
val saveResult = runBlocking { memberRepository.save(member) }
val findResult = runBlocking { memberRepository.findById(member.id) }
// Then
assertThat(saveResult).isInstanceOf<Result.Success<Unit>>()
assertThat(findResult).isInstanceOf<Result.Success<Member?>>()
val retrievedMember = (findResult as Result.Success).value
assertThat(retrievedMember?.id).isEqualTo(member.id)
assertThat(retrievedMember?.name).isEqualTo(member.name)
assertThat(retrievedMember?.email).isEqualTo(member.email)
}
}
Testcontainers als Goldstandard
Jede Interaktion mit externer Infrastruktur (DB, Cache, Broker) muss mit Testcontainers getestet werden.
@Testcontainers
class EventStoreIntegrationTest {
companion object {
@Container
@JvmStatic
private val redisContainer = GenericContainer<Nothing>("redis:7-alpine")
.withExposedPorts(6379)
@Container
@JvmStatic
private val kafkaContainer = KafkaContainer(DockerImageName.parse("confluentinc/cp-kafka:7.4.0"))
}
@Test
fun `should store and retrieve events from Redis`() {
println("[DEBUG_LOG] Testing Redis event storage")
// Given
val eventStore = RedisEventStore(
redisHost = redisContainer.host,
redisPort = redisContainer.getMappedPort(6379)
)
val event = MemberCreatedEvent(
memberId = MemberId.generate(),
name = "Test Member",
timestamp = Instant.now()
)
// When
val storeResult = runBlocking { eventStore.store(event) }
val retrieveResult = runBlocking { eventStore.getEvents(event.memberId) }
// Then
assertThat(storeResult).isInstanceOf<Result.Success<Unit>>()
assertThat(retrieveResult).isInstanceOf<Result.Success<List<DomainEvent>>>()
val events = (retrieveResult as Result.Success).value
assertThat(events).hasSize(1)
assertThat(events.first()).isInstanceOf<MemberCreatedEvent>()
println("[DEBUG_LOG] Successfully stored and retrieved ${events.size} events")
}
}
Debugging in Tests
Debug-Ausgaben im Test-Code müssen mit [DEBUG_LOG] beginnen, um sie leicht identifizieren und filtern zu können.
@Test
fun `should handle complex business scenario`() {
println("[DEBUG_LOG] Starting complex business scenario test")
// Test implementation
println("[DEBUG_LOG] Member created with ID: ${member.id}")
println("[DEBUG_LOG] Published ${events.size} domain events")
println("[DEBUG_LOG] Test completed successfully")
}
🎯 AI-Assistenten: Testing-Schnellreferenz
Test-Kategorien und Werkzeuge
| Test-Typ | Coverage-Ziel | Werkzeuge | Verwendung |
|---|---|---|---|
| Unit-Tests | 80%+ | JUnit 5, MockK, AssertJ | Domänen- & Anwendungslogik |
| Integrationstests | Alle Repositories | Testcontainers, JUnit 5 | Externe Integrationen |
| End-to-End Tests | Kritische User-Journeys | Testcontainers, REST Assured | Vollständige Workflows |
Testcontainer-Konfiguration
PostgresQL
@Container
private val postgresContainer = PostgreSQLContainer("postgres:16-alpine")
.withDatabaseName("testdb")
.withUsername("test")
.withPassword("test")
.withInitScript("test-data.sql")
Redis
@Container
private val redisContainer = GenericContainer<Nothing>("redis:7-alpine")
.withExposedPorts(6379)
.withCommand("redis-server", "--appendonly", "yes")
Kafka
@Container
private val kafkaContainer = KafkaContainer(DockerImageName.parse("confluentinc/cp-kafka:7.4.0"))
.withEnv("KAFKA_AUTO_CREATE_TOPICS_ENABLE", "true")
Keycloak
@Container
private val keycloakContainer = KeycloakContainer("quay.io/keycloak/keycloak:26.0.7")
.withRealmImportFile("test-realm.json")
.withAdminUsername("admin")
.withAdminPassword("admin")
Test-Patterns für Result-Handling
// Success-Case testen
@Test
fun `should return Success when operation succeeds`() {
// Given
every { dependency.operation() } returns Result.Success(expectedValue)
// When
val result = serviceUnderTest.performOperation()
// Then
assertThat(result).isInstanceOf<Result.Success<ExpectedType>>()
assertThat((result as Result.Success).value).isEqualTo(expectedValue)
}
// Failure-Case testen
@Test
fun `should return Failure when dependency fails`() {
// Given
every { dependency.operation() } returns Result.Failure(ExpectedError.SOME_ERROR)
// When
val result = serviceUnderTest.performOperation()
// Then
assertThat(result).isInstanceOf<Result.Failure<ExpectedError>>()
assertThat((result as Result.Failure).error).isEqualTo(ExpectedError.SOME_ERROR)
}
Mock-Setup für Services
class ServiceTest {
private val repository = mockk<Repository>()
private val eventPublisher = mockk<EventPublisher>()
private val externalService = mockk<ExternalService>()
private val serviceUnderTest = Service(repository, eventPublisher, externalService)
@BeforeEach
fun setup() {
clearAllMocks()
// Default mocks
every { eventPublisher.publish(any()) } returns Result.Success(Unit)
}
@AfterEach
fun cleanup() {
confirmVerified(repository, eventPublisher, externalService)
}
}
Testdaten-Builder
class MemberTestDataBuilder {
private var id: MemberId = MemberId.generate()
private var name: String = "Test Member"
private var email: String = "test@example.com"
private var status: MemberStatus = MemberStatus.ACTIVE
fun withId(id: MemberId) = apply { this.id = id }
fun withName(name: String) = apply { this.name = name }
fun withEmail(email: String) = apply { this.email = email }
fun withStatus(status: MemberStatus) = apply { this.status = status }
fun build() = Member(
id = id,
name = name,
email = email,
status = status
)
}
// Verwendung in Tests
@Test
fun `should validate member data`() {
val member = MemberTestDataBuilder()
.withName("Max Mustermann")
.withEmail("max@meldestelle.at")
.withStatus(MemberStatus.PENDING)
.build()
// Test implementation
}
Performance-Tests
@Test
fun `should handle high load efficiently`() {
println("[DEBUG_LOG] Starting performance test with 1000 concurrent operations")
val operations = (1..1000).map {
async {
serviceUnderTest.performOperation(
TestCommand(id = MemberId.generate())
)
}
}
val results = runBlocking {
operations.awaitAll()
}
val successCount = results.count { it is Result.Success }
val failureCount = results.count { it is Result.Failure }
println("[DEBUG_LOG] Performance test completed: $successCount successes, $failureCount failures")
assertThat(successCount).isGreaterThan(950) // 95% success rate minimum
}
Navigation:
- Master-Guideline - übergeordnete Projektrichtlinien
- Coding-Standards - Code-Qualitätsstandards
- Documentation-Standards - Dokumentationsrichtlinien
- Architecture-Principles - Architektur-Grundsätze