-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
Ideally our unit tests are simple enough that it's obvious which line failed and for what reason, but this isn't always the case. For example, some of the old DocumentSourceGroup tests give you almost no indication of what went wrong if the test fails. In this case, you need to resort to print statements or gdb to figure out what was going on.
- duplicates
-
SERVER-6024 unittest assertions (ASSERT_*) should collect stack traces before throwing exceptions.
- Closed