UUM-113257
Fixed in 6000.6.0a2Mentioned in 16 release notes.
First fixed in 6000.6.0a2 (Apr 2, 2026); relisted in 15 later releases.
| Version | Section | Risk | Impact | Note |
|---|---|---|---|---|
| 6000.6.0f1 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0b10 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0b9 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0b8 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0b7 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0b6 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0b5 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0b4 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0b3 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0b2 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0b1 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0a7 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0a6 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0a5 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0a3 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. | |
| 6000.6.0a2 | Fixes Test Framework | Fix | The parent nodes of a test run where there is an exception happening in OneTimeTearDown are now correctly reported as failed in the Test Runner window. |