3 ms·
I've had limited success. IME it's critical to make them as deterministic as possible without being too specific. Non-random test data coupled with 'id' attribu
by paulryanrogers 7y ago
I've had limited success. IME it's critical to make them as deterministic as possible without being too specific. Non-random test data coupled with 'id' attributes on interacted elements help a lot. Beyond that each webdriver abstraction has quirks one must learn.
Animations and rendering races are sticky points too. Usually it's possible to put in some strategic waits to get consistent results.
Lastly getting them running in parallel can be tough, but the payoff is usually worth it if the number of tests must grow beyond a few dozen.
- ethbro 7y agoIf your UX designers can stomach it, simply ensuring async actions have a defined signpost to signify completion is the most helpful. E.g. an element that shows up when results are finished loading on the page. "Spinner that disappears" isn't terrible, but isn't great either. "Everything looks the same, and then some results load, and more results might load at some point, maybe" is sadly not that rare.