Commit e887475f authored by Jamie Tanna's avatar Jamie Tanna
Browse files

Add more reasoning behind `abstract` tests

parent 7e374b1e
Pipeline #352671650 passed with stages
in 4 minutes and 22 seconds
......@@ -147,3 +147,10 @@ abstract class JsonTest {
// ...
}
```
However, this isn't always quite perfect, and so I'd recommend this pattern in the case that:
- You have more tests than makes sense to be `@ParameterizedTest` (maybe 4 sets of tests?)
- You want to have a more structured hierarchy / naming structure to your tests
- You need any shared functionality that could be utilised by `abstract` methods being used by other methods in the baseclass, such as `prettyPrint()` above.
- You definitely know you'll want to add tests in the child classes (i.e. `ScenarioOutlineWithDocstring`) that are extra to what is provided in the base class
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment