Not all reasons why a test may be considered risky are documented
sebastianbergmann opened this issue · 0 comments
sebastianbergmann commented
- Test did not perform any assertions but was expected to do so
- Test is not expected to perform assertions but performed assertions
- Test modified global state but was not expected to do so
- Test printed output
- Test code or tested code did not close its own output buffers
- Test code or tested code closed output buffers other than its own
- Test was aborted after timeout
- Test does not define a code coverage target but is expected to do so
- Test executed code that is not listed as code to be covered or used
- Test depends on a test that is larger than itself