Automation in Testing (AiT) is a new namespace designed by Richard Bradshaw and Mark Winteringham. The use of automation within testing is changing, and in our opinion, existing terminology such as “Test Automation” is tarnished and no longer fit for purpose. So instead of having lengthy discussions about what Test Automation is, we’ve created our own namespace which provides a holistic experienced view on how you can and should be utilising automation in your testing.
Automated Check Design is the process of designing which checks should be automated, and then how to go about designing them before we implement them. Automated Checks is our preferred terminology within AiT, but if it leaves you confused, change check to test, and re-read it, we’ll be talking about the same thing.
What You Will Learn On This Course:
The first half of about what and why. We’re going to explore which automated checks should be created, and in turn, which shouldn’t and importantly with both, why?
The second half of the day will be spent on how we go about implementing checks, from a design angle, and looking at all the factors that make up an automated check. By the end of the tutorial, attendees will be able to:
- Dissect existing automated checks to determine their purpose and intentions
- Show the value of automated checking
- Describe the anatomy of an automated check
- Discover opportunities to design automation to assist testing
- Distinguish between a check that provides value and one that doesn’t
- Appreciate that succeeding with automation requires far more than coding skills
What You Will Need To Bring:
Please bring a laptop, OS X, Linux or Windows with all the prerequisites installed that will be sent to you.
