ISSUE #26 - July 30, 2017
Testing the UI of a web application, or testing the behavior of the application via the UI (different but often overlapping activities), increasingly calls for automation to catch regression bugs, and to keep with agile delivery schedules. We look at a few aspects of UI test automation in this issue.
What is reasonable in UI automation testing? This post covers the situation of regression testing a mature app, including valuable explanation of daily test maintenance activities.
Amusing Valentine’s Day-themed post on UI-based test automation that makes serious points:
Why wouldn’t you just use a record-and-replay framework (Selenium IDE or similar) to generate your UI tests, it’s so much easier than designing page-object models and writing code, right? The answer is, they will break a lot, “because the information used to locate page elements keeps breaking”. Read the 2016 study here:
When is it worth testing via API (example uses Postman) rather than the UI?
How to reason through selecting UI vs API testing approach:
If end-to-end tests result in a slow and unreliable feedback loop for you, consider replacing them with contract based integration tests, with an example using Pact JS:
Mozilla post on cross browser compatibility, and a learning module on testing with SauceLabs and BrowserStack:
This is not specific to test automation, but a really good resource for any Web testing. It’s actually a Web developer’s checklist, but can double as a QA list of testing directions to consider:
Things worth learning: How to read and understand a scientific paper: a guide for non-scientists, with a usage example.
If you received this email directly then you’re already signed up, thanks! Else if this newsletter issue was forwarded to you and you’d like to get one weekly, then you can subscribe at http://testersdigest.mehras.net
If you come across content worth sharing, please send me a link at firstname.lastname@example.org