Testing

Running the tests

./gradlew test

Runs the tests across all modules. CI runs the same command; it’s a required check for merging to main.

What is tested today

The suite is small — being honest about that is more useful than implying coverage. What exists:

Module	Tests	Roughly what they cover
backend	CourseServiceTest, CodeServiceTest, LabServiceTest, ProblemServiceTest, LabHealthServiceTest, StudentIdentityServiceTest, ApiTokenStoreTest	Service-layer logic
backend	controller/HealthControllerTest	The /health endpoint (MockMvc slice)
cli	CliTest	CLI command behavior, with a fixture properties file and sample course YAML
kt-judge	JudgeParserTest	Parsing judge output into verdicts
kt-judge	JudgeControllerTest	The judge HTTP endpoints
frontend	ContrastRatioTest	Theme color-contrast logic (common test)

data has no tests.

How the tests are set up

• All JVM modules use JUnit 5 (useJUnitPlatform()).
• Backend and CLI tests use MockK and an H2 in-memory database instead of PostgreSQL.
• kt-judge uses springmockk (@MockkBean); both HealthControllerTest and JudgeControllerTest use @WebMvcTest + MockMvc.
• Frontend tests are Kotlin Multiplatform common tests (kotlin.test), so they run without a browser or desktop window.
• JudgeSelfTest in the judge’s main source is not a unit test — it backs the /selftest endpoint, which grades a known-good solution end to end to prove the judge can actually run a job.

Where the gaps are

No test exercises the full run/submit path (client → backend → judge → git). The session lifecycle, GitService storage, and the OAuth flow aren’t directly covered either. If you change any of those, verify by running the affected piece.