Describe the bug
When starting a new execution of a run, the per-step resolutions (passed / failed / skipped) from the previous execution are not reset. The steps carry over their old status instead of starting fresh, so a new run appears to already have results before the tester has done anything.
In the attached screenshot, this is a freshly started execution ("Manual tests at 17 Jul 2026 12:45 Copy"), yet the first step "Login as subdepartment department administrator" is still marked as passed (green checkmark) from the prior run.
To Reproduce
Steps to reproduce the behavior:
Open a manual test run and execute a test case, marking one or more individual steps as passed / failed / skipped.
Start a new execution of the same run (e.g. via copy / re-run).
Open the same test case in the new execution.
See that the step resolutions from the previous execution are still present instead of being cleared.
Expected behavior
When a new execution is started, all step resolutions should be reset to their default (unchecked / no result) state, so the tester begins from a clean slate. Only the overall run-level and test-level results should be tracked per execution; step statuses should not leak across executions.
Screenshots
Screenshot attached showing the new execution with the first step still marked passed from the previous run.
Desktop (please complete the following information):
OS: W11
Browser: Chrome
Browser Version: 150.0.7871.128
Application: prod
Additional context
The test-case-level result appears to reset correctly (the case shows as not-yet-run), but the individual step states do not, which suggests the reset logic covers the case/run level but misses the step level.
Describe the bug
When starting a new execution of a run, the per-step resolutions (passed / failed / skipped) from the previous execution are not reset. The steps carry over their old status instead of starting fresh, so a new run appears to already have results before the tester has done anything.
In the attached screenshot, this is a freshly started execution ("Manual tests at 17 Jul 2026 12:45 Copy"), yet the first step "Login as subdepartment department administrator" is still marked as passed (green checkmark) from the prior run.
To Reproduce
Steps to reproduce the behavior:
Open a manual test run and execute a test case, marking one or more individual steps as passed / failed / skipped.
Start a new execution of the same run (e.g. via copy / re-run).
Open the same test case in the new execution.
See that the step resolutions from the previous execution are still present instead of being cleared.
Expected behavior
When a new execution is started, all step resolutions should be reset to their default (unchecked / no result) state, so the tester begins from a clean slate. Only the overall run-level and test-level results should be tracked per execution; step statuses should not leak across executions.
Screenshots
Screenshot attached showing the new execution with the first step still marked passed from the previous run.
Desktop (please complete the following information):
OS: W11
Browser: Chrome
Browser Version: 150.0.7871.128
Application: prod
Additional context
The test-case-level result appears to reset correctly (the case shows as not-yet-run), but the individual step states do not, which suggests the reset logic covers the case/run level but misses the step level.