At the Quality in Agile Vancouver 2015 conference, Lisa Crispin and Janet Gregory facilitated an all-day workshop on advanced topics in agile testing with a focus on automation. Even if testers don’t write code, they need to participate in automating regression tests and other useful automation, in collaboration with programmers, business stakeholders and others.
This write-up recaps the workshop in which the two walked through ways that teams can overcome test automation challenges. They suggest getting your team together, trying out some brainstorming techniques, and making it comfortable and safe for each person to contribute their ideas.
For more key takeaways and advice, read the full article here.
If you take a step back to consider the entire purpose of a software tester, things can look a little grim. Your goal is to find the problems everyone else wish didn’t exist, the problems people wish were never found, the problems that the business wishes it didn’t have to deal with.
It seems as though every time something is under test, a layer of tension descends upon the workplace. People brace themselves and hope for the best. So how do you, as a tester, go about being positive in a negative testing world? In this post, author Rosie Sherry highlights the importance of celebrating both failures and successes, and leaves readers with valuable takeaways she’s collected during her 15+ years in the industry.
Frustrated by the organizational bias towards software testing that he has faced his entire career, Martin Hynie and his team decided to experiment with rotating job titles. They asked the question: “What if we did not call ourselves testers? Would anything change?” In other words, they had an interesting hypothesis about their system and like all good testers, they decided to test it in order to learn more about it.
Hynie recounted the story of this 18 month experiment at TestBash, and the Ministry of Testing has recently released his full presentation. In it, not only does he highlight the startling impact these title changes had on the members of the testing team, but he also touches on companywide reactions to his little experiment.
4. Discussion: When There’s No Designated QA
“In my company that I am currently working with, we have more than 30 developers and I am practically the only QA.”
This poster to the Software Testing Club forum is out to change the negative mindset many of her coworkers have around the saying, “QA is every single individual’s responsibility.”
She has proposed the plan of getting the dev teams to test each other’s work, but she has come across some roadblocks with this approach. She asks if anyone has faced something similar and requests feedback to help her change the situation.