Ran
|
Jobs
1
|
Files
11
|
Run time
1s
|
Badge
Embed ▾
README BADGES
|
push
travis-ci
<a href="https://github.com/apache/commons-csv/commit/<a class=hub.com/apache/commons-csv/commit/485929e626e479079b408501f7253ac4daedd3fc">485929e62<a href="https://github.com/apache/commons-csv/commit/485929e626e479079b408501f7253ac4daedd3fc">">CSV-252: Clean up exception handling (#50) * CSV-252: Clean up assertions using assertThrows As a followup to commit </a><a class="double-link" href="https://github.com/apache/commons-csv/commit/<a class="double-link" href="https://github.com/apache/commons-csv/commit/e2f0a4d8a83a41eaa984086636a3712c682307ea">e2f0a4d8a</a>">e2f0a4d8a</a><a href="https://github.com/apache/commons-csv/commit/485929e626e479079b408501f7253ac4daedd3fc"> that introduced JUnit Jupiter to the project, this patch leverages the new Assertions#assertThrows method to clean up tests for expected exceptions. Instead of the somewhat clunky structure common in JUnit 4 tests: ``` try { someMethod(); fail("SomeException should be thrown"); } catch (SomeException e) { // Expected... // Possibly some assertion on e } ``` JUnit Jupiter allows the following elegant syntax: ``` SomeException e = assertThrows(SomeException.class, () -> someMethod()); // Possibly some assertions on e ``` * CSV-252: Remove redundant throws clauses from tests
933 of 1004 relevant lines covered (92.93%)
0.93 hits per line
ID | Job ID | Ran | Files | Coverage | |
---|---|---|---|---|---|
2 | 289.2 | 11 |
92.93 |
Travis Job 289.2 |
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|