I only watched one webinar last week. However, I did find time to start work on a new side project. Continue reading to hear more…

Python Koans with Peet Michielsen

I’ve signed myself up to the #virtual-coffee channel on the Ministry of Testing slack. Each week, I am paired up with a different person within that channel. This week I was paired with Peet Michielsen. I first met Peet at UKSTAR 2019 where I watched his talk on improving the release pipelines. I was lucky enough to meet him again at Test Bash Manchester. We had a great conversation about unit tests during lean coffee.

Peet suggested a python programming session and pointed me in the direction of these python koans. I’d temporarily abandoned my python goal, so this seemed like a good way to get back into it. The python koans are full of tests which are failing. The goal is to fix them. Together we completed the chapters on dictionaries and string formatting. The next lesson is on Tuples, something I’ve written about before.

The python koans have inspired me to create something similar for C# and SpecFlow. This will be a fun side project which I hope will help testers gain confidence when they are introduced to automated tests for the first time. I’ve only just got started on this, but you will hear more about this in the future.

MOTrix – Skills To Pay The Bills with Gwen Diagram

In this talk, Gwen walks us through the process of identifying what the team needs to learn and then make arrangements to help them learn.

First, create a test strategy. Map out the current architecture to identify what the team already knows. Understand what testing already exists and how this fits in with the current strategy. Then, identify what the business goals are and the team needs to achieve to meet those goals.

Second, identify what is needed to help the team grow. What does the team need to learn? This should correlate with what individual members are interested, or not interested, in learning as well as the business goals.

Finally, arrange time and resources to allow the team to learn these skills. Setup internal coaching, identifying potential mentors within the team, arrange training sessions, and provide resources to help them learn. Set objectives to give the team and its members something to aim for. The ‘30 things every new software tester should learn‘ list could be a good start. Goals should be specific and clear. They can provide a clear direction of where the team needs to be.