Inline Expected Warnings in Tests
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating how tests currently declare and verify expected errors, then trace the warning-reporting path and the test entry points that consume it. Define how a warning's source line is specified and verified, with tests showing that expected warnings are detected at the requested line.
Written by the indexing model from the issue text.
Description
Besides expected errors, we could also check if a warning is reported in a specific line.
- Dominant language
- Java
- Stars
- 67
- Forks
- 36
- Avg merge
- 10d 18h
- Merged PRs (30d)
- 3
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.
More from liquid-java/liquidjava
-
enhancement
liquid-java/liquidjava#240 · 1 assignee ·
-
enhancement ide
Difficulty 3/5 1-2 days Newbie friendliness 45/100
liquid-java/liquidjava#206 ·
-
tests
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
liquid-java/liquidjava#198 ·
-
tests
Difficulty 4/5 3-5 days Newbie friendliness 25/100
liquid-java/liquidjava#197 ·
-
Improve Test Suite Openenhancement tests
liquid-java/liquidjava#174 · 1 comment · 1 assignee ·
All issues in liquid-java/liquidjava
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
enhancement Tools
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
apache/rocketmq-dashboard#5008 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
DETECT_PARAMETER_NAMES=false silently disables @ConstructorProperties-based Creator detection too Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FasterXML/jackson-databind#6229 ·