I've been struggling to find a "perfect" solution for real E2E testing Angular and had problems
- There seems to be no good published way (other than waiting on a specific element) to wait for the page to finish rendering before making assertions with Selenium
- On the other hand, no one talks about how to do real (against a live, local server) E2E testing with the scenario runner and in this case, how to control the consistency of the data when a test starts
In my searches, trying to find E2E scenario best practices, I thought I'd see how Angular tests their own web properties.
I'm wondering - what drove this decision?
Thanks
Georgios