Issue If a test run is completed, but the setting "Allow to add results for cases in closed runs", the wizard behaves inconsistently. If I click on a test that is still in "Untested" status, the wizard opens and allows me to add results to that test case. However, after submitting results to that test case, the wizard moves to the next Untested test case in a read-only view, forcing the tester to close the wizard and then reopen the wizard for each and every test case. Why wouldn't the wizard consistently allow updating test results for all Untested tests? Work around You can mark a single (or multiple) tests to "Rerun" which will re-open the whole test run; however, this seems unintuitive for cases where you don't need to retest, you just need to reopen the test run to complete what was left Untested when it was closed Request Can we either A) add a button to "Reopen" a test run rather than forcing a "Retest" action or B) update the wizard to be consistent when navigating to the next Untested test case automatically? Background Our team operates in a hybrid automation/manual test run flow (using Playwright). We originally set complete: false in the playwright reporter, since our test plans contain manual test cases that must be executed by the team prior to completing a test run. However, for teams that very frequently integrate code (good CI), they do not always complete the manual test case portions of every single test run that gets generated by the automated tests. Therefore, we'd like for the playwright reporter to auto-complete the test runs that are generated, and then only on the "latest" iteration for a release, the team can complete the manual portions of the test run. The current behavior of the wizard makes this experience clunky though.
