Set final_status for non-retry NUnit executions in ExecuteTest(), before FinishTest() closes the span, to avoid missing test.final_status in flaky CI snapshot runs.

Ensure NUnit writes test.final_status only on final retry executions, and stop writing it for non-retry and pre-execution skip paths to eliminate close-order race behavior and align with the feature contract. Update NUnit snapshot baselines to match the retry-only tag semantics.

… tests

Keep final_status retry-only for EFD, ATR, and ATF while setting final_status=skip for quarantined tests that do not retry, so quarantined outcomes remain queryable in CI Visibility.

…antics

Set test.final_status on executions that will not be retried anymore (including pre-skip and disabled paths) while keeping final-retry behavior for retry features. Update NUnit snapshot baselines and EVP metadata cleanup assertions so integration verification remains stable.

tonyredondo changed the title [Test Optimization] Stabilize NUnit final_status semantics NUnit: make test.final_status match the final test outcome

tonyredondo changed the title NUnit: make test.final_status match the final test outcome NUnit: emit test.final_status on terminal executions

Clarify that the non-retry branch only sets final_status when no retry will run, while final retry handling is performed in the isFinalExecution path below.