Add parameterized module: JUnit 5 @ParameterizedTest argument sources, display names, and two real anti-pattern failures
This commit is contained in:
@@ -0,0 +1,25 @@
|
||||
Captured from a real `junit-platform-console-standalone --details=tree` run against
|
||||
FieldSourceTest, compiled and executed for real.
|
||||
|
||||
╷
|
||||
├─ JUnit Platform Suite ✔
|
||||
├─ JUnit Jupiter ✔
|
||||
│ └─ FieldSourceTest ✔
|
||||
│ └─ shouldRecognizeIsoCurrencyCode(String) ✔
|
||||
│ ├─ ISO code "USD" should be recognized ✔
|
||||
│ ├─ ISO code "EUR" should be recognized ✔
|
||||
│ ├─ ISO code "GBP" should be recognized ✔
|
||||
│ ├─ ISO code "JPY" should be recognized ✔
|
||||
│ ├─ ISO code "INR" should be recognized ✔
|
||||
│ ├─ ISO code "AUD" should be recognized ✔
|
||||
│ └─ ISO code "CHF" should be recognized ✔
|
||||
└─ JUnit Vintage ✔
|
||||
|
||||
Test run finished after 217 ms
|
||||
[ 7 tests successful ]
|
||||
[ 0 tests failed ]
|
||||
|
||||
@FieldSource reads its arguments straight from a static field rather than a method or inline
|
||||
literals -- here FieldSourceTest's own static VALID_ISO_CODES field, which is kept in lock-step
|
||||
with the real Set CurrencyService.isValidCode checks against, so the seven invocations above are
|
||||
exactly the seven codes the real service recognizes.
|
||||
Reference in New Issue
Block a user