di-sukharev / di-sukharev/opencommit
[Feature]: Any hacker volunteers to add tests and make the world even a better place?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
It's now difficult to verify that you haven't broken anything by a PR.
current state of things requires to npm run build and then npm start to test a PR locally. It's bothering, more time-consuming then auto-tests and error-prone :(
Suggested Solution
I would use Jest + Testing Library to cover all the base scenarios, then add a GitHub Action to run the tests on a PR creation.
Alternatives
No response
Additional Context
No response
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 by running npm run build and npm start to understand the current local verification flow, then inspect the project’s existing test setup and PR automation. Done means base scenarios are covered with Jest and Testing Library, and a GitHub Action runs those tests when a PR is created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100