Test Public Methods
Open
Nobody has claimed this yet.
new check
- Dominant language
- ABAP
- Stars
- 435
- Forks
- 77
- PR merge metrics
- No merged PRs in 30d
Description
Based on the Test against interfaces, not implementations and Test publics, not private internals, an automated check is more than welcome to avoid unnecessary unit tests.
Ps: I see some tests going so deep, testing even the private methods with inheritance and friends, just to raise the coverage.
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
The issue names no files, tests, or entry points. Start by reading the linked Clean ABAP guidance on testing interfaces and public methods, then inspect how automated checks are organized in this project. Done means an automated check addresses unnecessary tests of private methods or implementations.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100