...
What was helpful vs unhelpful
Helpful - Clean test code
- All callback and domain classes are specific to test and organized as inner classes within the test class
- Use of non-deprecated APIs
- Use of AssertJ instead of Assert
| Unhelpful - Asynchronous activity
- Thread.sleep or Wait.pause calls
- Major refactorings such as modularization
- Non-thread-safe static product test hooks
- TestHelper classes and custom startup rules that configure processes or perform actions
- Generalized callback and domain classes reused by more than one test
- Tests that use dunit working directories instead of TemporaryFolder Rule
- Catching unexpected exceptions
- Instantiating a dunit class again from a static method
|
---|
What you can do to make things better?
...
{"serverDuration": 108, "requestCorrelationId": "61d2d594c2389109"}