open-feature / open-feature/cli
feat: integration tests for java generator
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 63
- Forks
- 22
- Avg merge
- 1h 27m
- Merged PRs (30d)
- 19
Description
feat: integration tests for java generator
Description
The CLI has adopted an integration testing pattern to validate that generated feature flag clients compile and function correctly within their respective language ecosystems. The Java generator does not yet have integration test coverage.
We should implement integration tests for the Java generator using the standardized approach outlined in the test suite documentation.
📄 Relevant Documentation:
Integration Testing Pattern
Tasks
- Create a test project scaffold for Java (e.g., using Maven or Gradle)
- Generate a feature flag client using the Java generator
- Compile and execute basic assertions (e.g., ensure the generated code builds, dependencies resolve, and a simple flag evaluation runs)
- Integrate this test into the broader test suite and CI workflow
- Add any Java-specific test setup or notes to the documentation if needed
Acceptance Criteria
- ✅ Java generator is covered by at least one integration test
- ✅ Generated Java code compiles and passes basic execution
- ✅ Integration test runs as part of the CI suite
- ✅ Test follows the documented integration testing structure
Additional Notes
Adding Java integration tests ensures that changes to the generator do not silently introduce regressions and increases confidence in the CLI's language support matrix.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with test/README.md and its documented integration testing structure. Create the Java test project, generate a client with the Java generator, compile and run basic flag-evaluation assertions, then integrate the test into the broader test suite and CI workflow. Done means the generated Java code builds, executes successfully, and runs in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java
- Domain
- ci-cd, cli, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100