Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
0.8.1.1
-
None
Description
The system test scripts don't handle errors well. A couple of key issues:
- Unexpected exceptions during tests are just ignored and the tests appear to be successful in the reports.
- The scripts exit code is always 0, even if tests fail.
- Almost no subprocess calls are checked. In a lot of cases this is ok, and sometimes it's not possible (e.g. after starting a long-running remote process), but in some cases such as calls to DumpLogSegments, the tests can miss that the tools is exiting with an exception and the test appears to be successful even though no data was verified.