Ready for another awesome 30 Days of Testing challenge?! Great! We've got a new challenge all ready for you to take part in! The theme this time is Agile Testing and this challenge has been kindly sponsored by TestRail.
Below is a list of 30 challenges and a bonus challenge, one for each day of the month. Download the PDF. Save it somewhere. Print it out. Stick it on your wall. Let’s do this!
What are the rules?
The goal is to tick off as many of the challenges as you can. You can do this 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 September 2017.
You may have an image to share, a blog post, a video, status update, whatever it is! Come and participate!
Here is how you can get involved and share your progress:
- On Instagram, Twitter, LinkedIn – use the #30DaysOfTesting hashtag
- On our 30 Days of Testing category in The Club
- Download the PDF
30 Days of Agile Testing, the text version
- Buy an agile testing related book and share something you’ve learnt by day 30
- Create a mindmap, document, diagram or sketchnote about what you think agile testing is
- Find a video on YouTube about agile testing, then watch it!
- Read the agile manifesto and reflect on the implications for your role
- Pair with a developer on a feature
- Map out what your exploratory testing looks like, compare it to what other testers do
- Find a visual way of representing your tests - e.g. a mind map, diagram, model, etc.
- Speak to a developer about a bug you found instead of logging it in the tracking system
- Pair with a developer on a code review. Can you identify any risks?
- Learn where the application logs are and how to read them
- Find out what customers are saying about your product. What did you learn?
- What test documentation does your team have? How can you improve it?
- Learn to use a tool that your developers use - e.g. an IDE
- How can you deliver greater value to your customer?
- How can you make your testing processes (more) lean?
- What barriers do you feel exist in testing in agile?
- Map out your current team structure. How does it compare to other teams?
- How can you make testing jobs easier?
- How can you make jobs for your team easier?
- Investigate what is in your and your team’s tool kit
- How are you managing your testing, is it really agile?
- Find out what testing is being done by other team members
- What agile strategies are there for managing tests? How can you improve yours?
- Look for a task that can be automated
- What can’t you automate? Communicate that to your team
- What does your Test Plan look like, what format do you use?
- Look into zero bug tolerance, is this something your team could do?
- What learning culture exists in your company? How can you contribute to it?
- What columns do you have on your work tracker or kanban board?
- What action does your team take on a red build?
- BONUS: Debrief your whole team on your last session of testing
