Forward unexpected exceptions instead of catching and failing
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 Forward unexpected exceptions instead of catching and failing, the unit test should focus on the happy path.
The new check can scan for try...catch in the test methods and inform the developer once it finds an assert fail within the catch.
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 with the linked CleanABAP.md guidance on forwarding unexpected exceptions, then inspect the repository's existing checks for test-method exception handling. Done means the new check identifies try...catch in test methods when the catch contains an assert fail and informs the developer.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100