Write Integration/E2E tests
Open
help wanted
- Dominant language
- TypeScript
- Stars
- 39
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Currently, `core` package is continuously changing, we need to have integration tests to make sure that new changes will not break the old features.
It's good to have [cypress](https://www.cypress.io/) tests on [example project](https://github.com/tuhuynh27/reactif/tree/master/example).
So after we have tests, we can perform CI tests check on every commits and pull requests.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining the core package and the example project, then review Cypress as the proposed integration-test tool. Define tests that protect existing example-project behavior after core changes, and verify that they run in CI for commits and pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, typescript
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100