Closed JSAbrahams closed 5 years ago
Merging #67 into master will decrease coverage by
0.36%
. The diff coverage is91.3%
.
@@ Coverage Diff @@
## master #67 +/- ##
==========================================
- Coverage 80.09% 79.72% -0.37%
==========================================
Files 57 57
Lines 3893 3847 -46
==========================================
- Hits 3118 3067 -51
- Misses 775 780 +5
Impacted Files | Coverage Ξ | |
---|---|---|
src/parser/mod.rs | 100% <ΓΈ> (ΓΈ) |
:arrow_up: |
tests/parser/valid/control_flow.rs | 87.07% <100%> (ΓΈ) |
:arrow_up: |
tests/parser/invalid/operation.rs | 100% <100%> (ΓΈ) |
:arrow_up: |
tests/parser/valid/collection.rs | 86.13% <100%> (ΓΈ) |
:arrow_up: |
tests/parser/mod.rs | 100% <100%> (ΓΈ) |
:arrow_up: |
tests/parser/invalid/function.rs | 100% <100%> (ΓΈ) |
:arrow_up: |
tests/parser/valid/compound.rs | 100% <100%> (ΓΈ) |
:arrow_up: |
tests/parser/invalid/expression_and_statement.rs | 100% <100%> (ΓΈ) |
:arrow_up: |
tests/main.rs | 93.75% <100%> (+18.75%) |
:arrow_up: |
tests/parser/invalid/compound.rs | 100% <100%> (ΓΈ) |
:arrow_up: |
... and 6 more |
Continue to review full report at Codecov.
Legend - Click here to learn more
Ξ = absolute <relative> (impact)
,ΓΈ = not affected
,? = missing data
Powered by Codecov. Last update e612251...fdc9c89. Read the comment docs.
Relevant issues
One issue in #61 is that when looking at the Travis build it was not easy to deduce what went wrong since we don't output what happens when accessing test resources goes awry. Furthermore, this works towards #63 .
Summary
assert_eq!
by simply usingunwrap_err()
, which panics if we do not have an error. This is relevant for the invalid parser tests, which verify that incorrect syntax results in aParseErr
.panic
messages for when accessing test resources goes awry.assert_ok!
macroAdded Tests
No tests added, but some existing tests have been simplified.
Additional Context
...