Add parameterized module: JUnit 5 @ParameterizedTest argument sources, display names, and two real anti-pattern failures
This commit is contained in:
@@ -0,0 +1,20 @@
|
||||
Captured from a real `junit-platform-console-standalone --details=tree` run against
|
||||
CsvSourceTest#shouldAddNumbers, compiled and executed for real.
|
||||
|
||||
╷
|
||||
├─ JUnit Platform Suite ✔
|
||||
├─ JUnit Jupiter ✔
|
||||
│ └─ CsvSourceTest ✔
|
||||
│ └─ shouldAddNumbers(int, int, int) ✔
|
||||
│ ├─ "10" + "5" = "15" ✔
|
||||
│ ├─ "0" + "0" = "0" ✔
|
||||
│ ├─ "-3" + "7" = "4" ✔
|
||||
│ └─ "100" + "-50" = "50" ✔
|
||||
└─ JUnit Vintage ✔
|
||||
|
||||
Test run finished after 228 ms
|
||||
[ 4 tests successful ]
|
||||
[ 0 tests failed ]
|
||||
|
||||
The plainest @CsvSource shape: one inline comma-separated row per invocation, three columns
|
||||
mapped positionally onto the method's three int parameters, no header row involved at all.
|
||||
Reference in New Issue
Block a user