Testing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 22
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Adding tests to PEPhub would bring many benefits. It will be easier for developers to make changes without introducing bugs, and make releases without bugs.
We have many units in PEPhub, so there will be a significant amount of work required to add tests. I would suggest to added tests in the future PEPhub releases.
For unit tests I think we can use mock tests. But if we want to test whole pephub with real data and db, we will have to create dev database.
Will be happy to hear your ideas and suggestions.
Contributor guide
No contributing guide indexed for this repository
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 inventorying PEPhub's units and deciding which areas need coverage first. Compare mock-based unit tests with tests using real data and a development database; done requires an agreed testing scope and tests covering the selected units.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100