Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bot Run assignment issues with VoiceOver #1270

Open
howard-e opened this issue Nov 6, 2024 · 0 comments
Open

Bot Run assignment issues with VoiceOver #1270

howard-e opened this issue Nov 6, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@howard-e
Copy link
Contributor

howard-e commented Nov 6, 2024

Bot run oddities observed during today's CG meeting:

  1. 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].
  2. Afterwards, the results of that bot run was assigned to Isa which expectedly had no results populated, to be evaluated.
  3. 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:

  1. Investigate why the VoiceOver bot failed (logs above in no.1).
  2. 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.
  3. Prevent the bot's run from being assigned until it is fully completed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

1 participant