30 Days of Automation in Testing, Are You Taking Part?

Our famous 30 Days of Testing Challenge is back this JULY!  This time we're focussing on Automation in Testing and this challenge has been written by the AIT gurus themselves; Richard Bradshaw and Mark Winteringham. What's more, this challenge has been kindly sponsored by SmartBear... thank you!

What's #30DaysOfTesting challenge about?

Our 30 Days of Testing Challenge does what it says on the tin; in 30 days, try and check off as many of the testing challenges set as you can!

Why take part?

These challenges are awesome at helping testers explore specific testing topics and learn collaboratively with the rest of the testing community. They also take the hard work out of how to get started with learning testing topics by tasking you with daily bite-sized challenges. 

Who can take part?

Everyone can take part! 30 Days of Testing Challenges are suitable for those who are new to the testing topic, those who want to brush up their skills and even the experts in the field can get great value out of taking part and joining in on the community conversations around the challenge by following the #30DaysOfTesting hashtag on InstagramTwitterLinkedIn

How can I take part?!

Go to the 30 Days of Automation in Testing Challenge, find the list of 30 challenges (plus a bonus challenge!), one for each day of the month. Download the PDF. Save it somewhere. Print it out. Stick it on your wall. Get your team Involved!

The goal is to tick off as many of the challenges as you can. You can, of course, do this on your own and in your own timeframe, or you can join us in our joint community effort! We will be encouraging the community to share their progress on this challenge from the 1st of July 2018

If you're taking part in the community effort, you may have an image to share as you complete the tasks, maybe a blog post, a video or status update about your challenge journey... whatever it is tag us online, use the hashtag and get involved!  

Here is how you can share your progress: