You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Contextualizing the top comment some more. This issue only applies to runs done by a bot. The ability to edit the AT and Browser version for tester manually assigned runs hasn't been affected.
After w3c/aria-at-app#1279 is merged and deployed, it should now address that case for the bot.
@mcking65 after checking what went wrong, and discussing internally -- have found that this was not a regression as originally thought, but done by design. Any results produced by a bot was never expected to have a change for the specific AT and Browser versions, even when assigned to a tester to be evaluated. But the scenario discussed in yesterday's meeting is certainly reasonable.
The unique but likely case this now produces is there may be a combination of bot produced and manual-tester produced results which will give no clear indication of which specific AT or Browser Version actually produced the results shown for the commands' outputs.
I've started drafting w3c/aria-at-app#1280 in case we think this is something key to highlight when presenting finalized reports.
There is no longer a dialog (when entering a test plan) or a button while completing the test plan to update the AT version or browser version.
The text was updated successfully, but these errors were encountered: