Create E2E Fixture
Steps
Identify the test case: What behavior needs testing across language bindings?
Choose category: smoke, basic, parsing, edge-case, error-handling, or platform-specific.
Write fixture JSON:
{ "id": "descriptive_snake_case_name", "category": "basic", "description": "Tests that X produces Y", "source_code": "input data or code", "assertions": { "tree_not_null": true, "expect_error": false }, "tags": ["regression"] }Add to fixtures directory: Place in appropriate category file or subdirectory.
Regenerate: Run
task e2e:generate.Verify: Run
task e2e:testto confirm all languages pass.Commit: Include fixture + regenerated test files in same commit.
Guidelines
- IDs must be unique across all fixture files
- Include both positive and negative test cases
- Add skip conditions for platform-specific behavior
- Keep source_code minimal — test one thing per fixture