sub-test-engineer

Type-driven test generation uses type information, enums, and sealed classes to automatically discover test targets and validate paths across Java, Kotlin, TypeScript, and Go backends. It analyzes the codebase structure to plan a targeted test strategy.

Yes, you can automate test generation and mutation testing across multi-module projects. The workflow integrates with common build tools like Gradle and Maven, running in CI pipelines to iterate on surviving mutations and strengthen test coverage.

The best way to close coverage gaps is through gap-based refinement, which iterates on uncovered paths and surviving mutations. This approach targets specific weaknesses in your tests, refining them until configurable coverage goals are met.

Yes, ast-grep is required to run type-aware test generation and derive type information for test planning. Optional ClassGraph enrichment can be added to further enhance type discovery capabilities across your backend modules.

Yes, this test automation workflow supports Docker and integrates directly into CI pipelines. It operates across multi-module projects using dependencies like jq, Gradle, and Maven to execute automated test generation and validation.

Automated tests often miss edge cases when type information is not fully utilized. By using type-driven generation guided by sealed classes and validation annotations, the workflow ensures these specific edge cases are discovered and covered during the strategy phase.