Don't test private functions
Open
Nobody has claimed this yet.
team-wallet-framework
wf-test-quality-improvement
- Dominant language
- TypeScript
- Stars
- 413
- Forks
- 308
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 253
Description
All code should be reachable by public functions, by testing the expected behaviour of each method. If some internal operation is too complex to be tested this way, it should be refactored into a separate module instead, so that it can be fully tested and documented on its own.
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
No files, tests, or entry points are named. Start by locating tests that call private functions and identify the public behavior they should cover; done means internal operations are exercised through public functions, or are moved into separately testable and documented modules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100