Over a million developers have joined DZone.

30 Day Testing Challenge

DZone's Guide to

30 Day Testing Challenge

The Ministry of Testing has called all testers to take a 30-day testing challenge. Check it out and think about joining in.

· DevOps Zone
Free Resource

Download the blueprint that can take a company of any maturity level all the way up to enterprise-scale continuous delivery using a combination of Automic Release Automation, Automic’s 20+ years of business automation experience, and the proven tools and practices the company is already leveraging.

The Ministry of Testing has called all testers to take a 30-day testing challenge. For each day of July, there is a new task to do related to the world of testing. At Abstracta, we decided, since we test Monday through Friday anyway, why not join in on the fun? The challenge will ultimately help us to become better testers, which is what we always strive to do.

Tasks and Schedule of the Testing Challenge

Image title

Image Source: Ministry of Testing

When we saw the testing challenge, we said:

challenge accepted

So, we printed out dozens of copies of the challenge and hung them all over our offices, encouraging all of our testers to participate. Some of our teams have created groups that want to compete against each other in some (hopefully healthy) competition to amp up the motivation to complete it. Starting today, we will be working on each task every day, updating this post once a week with our progress and using the hashtag, #30daysoftesting on social media. Will you take the challenge?

For more information about the rules, go here.

Download the ‘Practical Blueprint to Continuous Delivery’ to learn how Automic Release Automation can help you begin or continue your company’s digital transformation.

testing ,social media

Published at DZone with permission of Federico Toledo, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}