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
As a developer or tester using argos ci in cypress, I would like to see better feedback when argosScreenshot times out due to aria-busy tags being present, so that I can quickly identify what is causing the timeout and fix it.
Description
I'm new to argos (and cypress), and I just spent a fair amount of time trying to work out why my argosScreenshot was timing out, but when using the built-in cy.screenshot it didn't. By looking through the code on GitHub and reading the docs, I eventually realised that I had an element with an aria-busy that became hidden but remained in the dom.
An error message telling me why the timeout occurred would have saved me a lot of time!
As a developer or tester using argos ci in cypress, I would like to see better feedback when argosScreenshot times out due to aria-busy tags being present, so that I can quickly identify what is causing the timeout and fix it.
Description
I'm new to argos (and cypress), and I just spent a fair amount of time trying to work out why my argosScreenshot was timing out, but when using the built-in cy.screenshot it didn't. By looking through the code on GitHub and reading the docs, I eventually realised that I had an element with an aria-busy that became hidden but remained in the dom.
An error message telling me why the timeout occurred would have saved me a lot of time!
Thank you for the great tool.