The following will be a regular feature where we share articles, podcasts, and webinars of interest from the web.
In this short piece, Michael Sowers challenges the readers to consider updating their telemetry based on organizational change. In particular, start with the following criteria: (1) providing teams with quick feedback on how the quality of the project, product, and user stories is progressing; (2) understanding how the teams are progressing and what the roadblocks are; (3) knowing how effective and efficient the teams’ processes are; and, (4) understanding resource consumption, both human and computer.
Gojko Adzic has partnered with Specflow for a series of articles to help people get the most out of Gherkin with some tips and tricks. Each week he will post a challenge for readers to answer about a particular example of Gherkin. In the first challenge, the reader must try to explain a missing value (A “Given” for a value that’s not supposed to be there).
Selenium is a set of tools used in support of automation. In this article, Manoj walks us through several of the changes coming to selenium. Relative locators will be a welcome update as well as installing / uninstalling add-ons for Firefox at runtime. The biggest may very well be the ability to use Docker to spin up containers. Anyone interested in checking out the changes can go to Selenium.dev for more details.
Bas Djikstra posts again about the costs and misconceptions around test automation – namely that it’s the end goal and not a means to an end. Investing in automation testing has associated long-term maintenance costs and it shouldn’t be considered the only type of validation performed by a team. Great advice in this piece on scaling automation.
In this article by Nataliia Syvynska explains two types of balance in web design: symmetrical balance and asymmetrical balance. In symmetrical balance elements are equally disposed on either side of the center (vertically and horizontally). Asymmetrical balance is focus on one particular object with several elements. The article raises an interesting question about validations from a UI/UX perspective of how the user interacts with the system in a “pleasing” fashion.