Menu
Conventions for using parallelization in all tests using Jupiter
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Conventions for using Kotlin
Conventions for Angular applications
Conventions for dependency injection and mocking in Spring Boot integration tests in this project. Use this whenever writing, reviewing, or refactoring integration test classes (anything annotated @SpringBootTest, or under src/test that talks to a real Spring context), especially when deciding how to wire dependencies or mock collaborators. Also consult this before adding @Autowired, @MockBean, @MockitoBean, or field injection in any test class.
| name | parallelization |
| description | Conventions for using parallelization in all tests using Jupiter |
Filename should be: junit-platform.properties and it should be placed in src/test/resources of each module.
Its content should be:
junit.jupiter.execution.parallel.enabled = true
junit.jupiter.execution.parallel.config.fixed.parallelism = 4
junit.jupiter.execution.parallel.config.dynamic.factor = 4.0
junit.jupiter.execution.parallel.mode.default = concurrent
junit.jupiter.execution.parallel.mode.classes.default = concurrent
Only add this file, and if the file doesn't exist. Do not override existing files.
Check if tests run successfully for every module where you add this file. If it fails, then remove the file.