Generally speaking, test automation means doing functional testing through the UI. Non-UI automation tends to be easier and more inherently stable and should also always be looked at in addition to UI automation. Continue reading
Action Based Testing is the secret sauce that makes TestArchitect a winning recipe for test teams. Find out how to apply ABT in your testing regimen with this infographic.
A major contributor to success in test automation is test design. If tests have many unnecessary detailed steps and checks, even a skilled automation engineer will not be able to make the automation efficient and maintainable.
In his latest TechWell column, Hans Buwalda discusses multi-station testing with actions, in particular using the “lead-deputy model.” In this model, a lead machine is responsible for most of the UI interaction of a test, but will also assign commands to the one or more “deputy” machines. The “deputy” machines work like normal test machines and are able to interpret and execute actions. They can work in sync with the lead machine, or in parallel.
Hans Buwalda draws from his “Three Holy Grails” analogy when he focuses on the key goals when creating a test design.