Test Automation

In this podcast I discuss test automation biases and how to avoid them.

TLDR; Kerry McKeever explained and demonstrated his AG Grid automation plugin for Cypress, showing where to find the code and how to create custom commands for cypress.

TLDR; Can Test Automation mind defects? Yes, both regressions and new defects by adding more variation into the paths or data used.

Statements like “Test automation should-not/can-not/will-not find defects” do not completely match my experience. In my experience, Automated Execution can be used to help find defects and frequently does. Not just ‘regressions’ but ’new defects’ as well.

TLDR; If you are lucky enough to already be working in testing, and want to learn to automate, then I recommend gradually automating to add value in your existing work. Focus on a few tools and approaches that add value to you. Then build on that.

TLDR; JUnit is an execution framework. The principles of TDD are about writing code, seeing it fail, writing code to make it pass, seeing it pass and making it better. All applies when writing automated execution code for Testing

Sometimes we ask for something, without really understanding what that means. Asking for collaboration opens more options.

TLDR; Release of my open source API Workshops.

I was asked how I might go about automating an online calculator application. I have a calculator app of my own so I was interested in comparing the two apps and experimenting with a canvas based JS App.

Much of “Test Automation” falls into the set of “Automated Execution to Detect Change”, in this post I will explain what that means and provide some examples.