The #30DaysOfTesting challenge was developed by Rob Meaney and Ash Winter. It was first launched by the Ministry of Testing in March 2019. Due to other committments, I’ve not been able to complete it in 30 days however I am slowly working through the list.
Analysing the list, I’ve split the tasks into 3 categories. This will help me fit the tasks around the projects I am currently working on.
- Learning more about Testability
- Working with colleagues
- Learning more about the application and the people who use it
I am also keeping a library of articles, blogs, videos, podcasts and other items related to Testability that have helped me complete the challenge. Click here to view the list.
Learning more about Testability
1 – Define Testability
3 – Begin reading a book related to testability and share your learnings by Day 30.
8 – Share a video about testability with your testing peers at your company.
10 – Follow and share three people on LinkedIn who regularly talk about testability
12 – Decomposability is an important part of testability. Complete our circuit breakers testing exercise over on the club
14 – Watch the Testability Ask me Anything on the Dojo. Post any additional questions on The Club
15 – Share a blog post that you found interesting related to testability.
23 – Share an article about application log levels and how they can be applied.
Working with colleagues
9 – In your next story kick off session ask, ‘how are we going to test this?’ Share the test ideas and techniques that are suggested.
11 – Get access to your source control and find the active branches for your application. Has anything changed that you didn’t consider?
16 – Conduct a show and tell of the latest features in your application for staff outside your immediate team. Capture their feedback and share with your team.
17 – Pair with a developer to see if they can improve something that you find difficult or time consuming to test.
18 – Note the top 3 challenges while testing and raise them at the team retrospective.
21 – Unit tests provide insight into an applications testability. Pair with a developer to explore some unit tests.
22 – How long does it take to set up a new test environment and start testing? Could this be faster?
25 – Ask your team if there are any areas of the system they fear to change. How could you mitigate that fear?
26 – Relationships with other teams affect testability. Share your experiences.
27 – Use source control history to find out which parts of your system change most often. Compare with your regression test coverage.
Bonus – Arrange a meeting with your team to take the team testability test over at http://testabilityquestions.com
Learning more about the application and the people who use it
2 – perform some testing on your application, then open your applications log files. Can you find the actions you performed in the logs?
4 – Do you know what your top three customer impacting issues are? How could you find out?
5 – What monitoring system is used for your application? Do the alerts it has configured reflect what you test?
6 – Export the output of your applications analytics, how can they help guide your testing?
7 – Find out if your application has an operational manual or runbook? How can you test this?
13 – Find out how test data is populated in your system. How could it be improved?
19 – Your dependencies can constrain your testability. Head over the The Club to visualise your applications boundaries.
20 – Think about what’s currently stopping your from achieving higher testability. Share your findings on the Club.
24 – What could you learn about your applications testability from being on call for support?
28 – Pair with an internal user or customer support person and explore your application together. Share your findings on The Club.
29 – Do you know which components of application respond the slowest? How could you find out?