Rosie is founder of Ministry of Testing (www.ministryoftesting.com) and an unschooling mother to 4 amazing children. She use to be a software tester, but now runs the growing Ministry of Testing whilst also unschooling her kids.You can find her on personally on @rosiesherry, RosieLand (www.rosiesherry.com) and UnschoolMe (www.unschool.me).
Olof Svedström has worked as an engineering lead within software testing and quality at Spotify for 5 years, during a period when he has been part of the journey where they have grown from 5 to 100 million active users and from 150 to 2000+ employees. Before Spotify he spent some years as a tester in a spectrum of companies, ranging from small product ones to international giants.
Spent half an hour talking to Katrina about software testing.
How did you get into Context Driven Testing?
Why do you speak at conferences?
What advice would you give to someone who is in the first year of their testing career?
What is your biggest achievement of your testing career?
What’s the best thing about coaching a team of testers?
And what’s the most difficult?
What made you decide to start blogging about testing?
What do you wish more people knew about software testing?
Do you see a problem in the gender ratio in testing?
If so, why? If not, why not? If so, how do you suggest we address this?
What, do you believe, are the 3 most important traits in a tester?
Do you think it’s possible to be a CDT but not Agile? vice versa?
- I am the only tester in an agile organisation with only developers and POs. How do I get mentored, because most people here do not understand testing.
Shirley Tricker worked in a wide range of IT roles for almost 20 years before starting Elementum, a business that helps people in IT to develop skills, attitudes and habits to be productive and happy in tech roles. Shirley is active in the testing community as an organizer of the Auckland chapter of WeTest, an attendee at the KWST peer conference, and she runs the Auckland Testers Facebook page.She is also co-organiser of the Women in Tech Auckland meetup and she speaks to students via the ICT-Connect programme, which inspires and educates young people about a future in IT. She recently started blogging where she advocates for people to take back control of their careers and work happiness.
Kim Engel is a software test manager focused on user experience and fostering communication between stakeholders.
She is a regular attendee of the OZWST peer conference, an avid reader and occasional writer of testing blogs, and an infrequent tweeter @kengel100.
Kim is in the process of overcoming 10+ years of traditional testing experience to adopt a Context Driven approach to Testing.
What was the hardest part about the transition from a traditional Test Manager to a Context Driven Test Manager?
Aaron Hodder is an experienced and passionate context-driven tester. Before joining Assurity, Aaron worked at Metra Weather as a Test Analyst for the Weatherscape XT product, a weather graphics presentation system used by TV stations nationwide.
Aaron is active in the testing community, having co-founded WeTest, attending the peer conference KWST and presenting at STANZ on using Lean Visual methods to plan and report on testing activities. Aaron will be giving a presentation at CAST 2013 on Mind Maps – A practical, lean, visual tool for test planning and reporting
How did you find yourself being an advocate of Context Driven Testing?
When I started out testing, I was one of three testers in an organisation of around 50 developers. The testing budgets I was given was often in the order of hours or days, not of weeks or months. It was an environment where I put my hand up to be a tester, and now suddenly had to learn what testing actually was. I was very insecure for several months. I was testing in a primarily exploratory manner, and talking directly with developers, but I was worried, after all, the textbooks told me I should be writing test plans, and I should be writing test scripts with expected results, and pre-conditions. But it wasn’t working for me.
To write the test script, I had to interact with the application and learn about it. Then I would write the script. But I had already performed the test I was about to script! At a conference, I timidly approached James Bach, and expressed my concern that I wasn’t testing “by the book”. He responded, “Why would you want to test by the book? The books are wrong!”
At that moment, a door opened, and I realised that I could set up my own sail, and develop my own ideas on what testing could be; that what constituted good testing depends on the context you find yourself in. I started seeing other testers around me in other organisations writing massive test documents and saw it for what it was: mostly ceremonial paper pushing.
It was then I realised there are two futures in my chosen profession. A future in which software testers are interchangeable commodities performing clerical superficial checks and wasting a lot of money, or a future in which software testers are respected and skilled members of a software development team who bring their critical and lateral thinking skills to bear to find problems noone thought about. I know which I want to be a part of, and I try to bring as many people along with me.