So, I’m the only tester in my department (it’s traditionally been more prototype stuff, so most teams don’t produce products as such, so, no testers. They are now shifting in focus to deliver things to other teams within the company).
I’ve been on a bit of a mission to increase the visibility of what testers do and why I think they should be thinking about testing. I gave a quick lunch and learn talk on testing, which you can see here: [https://docs.google.com/presentation/d/1sGipJBAK9Nm-mD6qQUCQNggUuJNBRTX4akPQD2bxy0Q/edit?usp=sharing](http://Google Drive link)
A team that have no testers and are just starting to build a test strategy, starting with unit tests, have asked me to help them. They’re currently doing some ‘ways of working’ meetings and want me to come along to a couple of them to help. I asked if anyone else had experience with teaching people how to test - especially when my time with them will be limited and there almost definitely won’t be a tester on the team going forward.
- First get their thoughts/ideas/current practices
— What are their unit tests like, what other skills are in the team, any testing experience elsewhere, what their thoughts are about what testing is
— Educate as needed. Throw some blog posts at them if they want (thinking Maaret P and Katrina Clokie to start with as they’re big on getting non-testers to test).
- Do some sessions around risk (maybe riskstorming) and non functional requirements
- Get them to consider their pipeline from idea to production, and figure out where testing activities can fit, what they currently do, what they can do: coupled with the risks I think this could be quite powerful
- See what comes out and iterate as needed
Apologies for the wall o’ text but what do people think? Anyone else have any experience of things like this?
(I’m aware this is an amazing position to be in and don’t want to mess it up)