objectionary / objectionary/lints
unit tests without asserts should be prohibited
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 14
- Forks
- 39
- Avg merge
- 22h 54m
- Merged PRs (30d)
- 90
Description
Consider this EO test:
+tests
# Test
[] > checks-something
52 > @
This test has no assertions, so it does not test anything. Let's complain about such situations if test object don't have any assertions inside.
Correct test should be:
+test
# Test
[] > checks-something
eq. > @
42
42
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 from the EO test examples in this issue and inspect the existing test-object linting entry point and related rule tests. Done means a test object with no assertions is reported, while the corrected example containing eq. is accepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100