Repository navigation
[P2] Validate & harden Java/JS adapters end-to-end #16
Description
Problem
Java (JUnit) and JS/TS (Jest) adapters are marked Beta and unproven end-to-end (generate→write→run→parse).
Tasks
- End-to-end test each adapter on a tiny sample project.
- Verify result parsing for non-pytest runners.
- Fixtures/mocks per framework.
- Promote beta→stable in README once green.
Acceptance
Each adapter generates and runs passing tests on its sample project in CI.
Activity
docs(bench): 20-run variance report + first empirical partitioning of…
pro-utkarshM commentedon Oct 15, 2026
Status: deferred to after v1. v1 is scoped to Python (
docs/task.md, README "Limitations").The Jest and JUnit adapters (
code2test/adapters/) and their templates are still in the code. They aren't wired into generation or verification:code2test testpasses only Python components to the pipeline and says so when it skips others. The README no longer calls them beta.Keeping this open as the post-v1 tracking issue for Java and JavaScript/TypeScript support.
Generated by Claude Code