liquid-java / liquid-java/liquidjava
Diagnostic Based Test Results
Open
tests
- Dominant language
- Java
- Stars
- 67
- Forks
- 36
- Avg merge
- 10d 18h
- Merged PRs (30d)
- 3
Description
Instead of determining whether a test should pass or fail based on its file or directory name, all tests could be treated the same way. Each test fails if an expected diagnostic is not reported (false negative) or if a diagnostic is reported without a corresponding comment (false positive).
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
No source files or test entry points are named in the issue. Review the open pull request #293 first, then trace the test-result logic and its existing diagnostic-based tests; the work is done when results no longer depend on file or directory names and false positives and false negatives are detected as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100