How to *properly* test quickly updating UIs #18181
Unanswered
mduft
asked this question in
Component Testing
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey,
We have an angular application under test. In some cases we have actions that have an immediate effect on the UI, e.g. adding or removing a row from a table due to data changes in the backend. In the test we trigger the according action and then have a check like this:
cy.contains('tr', 'default').click();
In rare cases we get a detached DOM element due to changing data in the service(s) and thus updating of the UI (rapidly):
The application re-created the table contents in this case due to some data change in the application, which is invisible to a user, but affects cypress a lot. How can we avoid this situation all together?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions