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
Admin @IsaDC assigned VoiceOver Bot to "Action Menu Button Example Using element.focus() - V24.10.31 for VoiceOver + Safari". The bot reported 1 error and 10 tests cancelled, for the 11 tests in the test plan. [View logs on that failed run].
Afterwards, the results of that bot run was assigned to Isa which expectedly had no results populated, to be evaluated.
Isa's run was then removed and a new run created. It was then immediately assigned to IsaDC to be evaluated. This run was successful but it was able to be assigned before the run was completed. That doesn't impact the results being populated, but this is a particularly confusing case when the expectation is that a bot's results can only be assigned and evaluated AFTER the bot run has been completed [View logs on that successful run]
TODO:
Investigate why the VoiceOver bot failed (logs above in no.1).
Investigate @mcking65's report on why the 'Manage Bot Run' button didn't appear so the option to re-run the bot's results collection could be used.
Prevent the bot's run from being assigned until it is fully completed.
The text was updated successfully, but these errors were encountered:
Bot run oddities observed during today's CG meeting:
VoiceOver Bot
to "Action Menu Button Example Using element.focus() - V24.10.31 for VoiceOver + Safari". The bot reported 1 error and 10 tests cancelled, for the 11 tests in the test plan. [View logs on that failed run].TODO:
The text was updated successfully, but these errors were encountered: