open-feature / open-feature/cli
feat: integration tests for react 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 react generator
Description
The CLI supports an integration testing framework designed to validate that generated feature flag clients are usable and functional within their target environments. Currently, the React generator lacks integration test coverage.
We should create an integration test for the React generator following the structure outlined in the testing documentation.
📄 Relevant Documentation:
Integration Testing Pattern
Tasks
- Scaffold a minimal React test app (e.g., using
create-react-apporVite) - Generate a feature flag client using the React generator
- Validate that the generated client compiles and integrates with a simple component
- Write a basic test to verify flag evaluation in the React environment
- Add the test to the integration test suite and CI
- Update documentation if needed for React-specific setup
Acceptance Criteria
- ✅ React generator has at least one integration test
- ✅ Generated React code integrates into a functional React component
- ✅ Integration test runs successfully in the CI pipeline
- ✅ The test adheres to the CLI's integration test pattern
Additional Notes
This test ensures that the React generator produces code that works correctly in a modern front-end stack and helps prevent regressions related to JSX integration or runtime behavior.
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 compare the existing integration tests with the React generator entry point. Scaffold the minimal React app, generate the client, and verify component integration and flag evaluation; done means the test is included in the integration suite and passes in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, react
- Domain
- ci-cd, cli, frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100