Hanser, the publisher, interviewed me about software testing: creativity, agile projects, the tester’s influence and the challenges ahead. The interview first appeared in 2015 on the “Hanser-Update” blog. My takeaway: with unit tests and TDD, developers are taking on more of the quality work, and that gives testers room for good test design and the user’s point of view. What they need most for that is creativity.
Software Testing in an Interview: Agile, Automation, Creativity
Mr. Seidl, Which Topics Are Currently Hotly Debated in Software Testing?
Right now I see two topics that testers around me are wrestling with:
- How do I make the switch as a tester from a traditional project to an agile one?
- How do I get test automation to really take off?
… Could You Briefly Outline Both Topics for Our Readers?
Some testers make the move into an agile environment effortlessly and are excited about the new possibilities. But just as agile projects are no cure-all, there are testers who can’t do much with this approach and feel lost in agile projects. Training such as the Certified Agile Tester is a solid foundation for understanding it, but it can’t address the concrete situations and problems of day-to-day work. My advice to testers in that situation is to take a close look at the values, concepts and motivation behind the agile approach. There is so much more to it than a different process. It can also help to ask: How can I best bring my skills into the project to increase its value and quality, maybe even in an unconventional, new way?
If that doesn’t get you anywhere, you can still ask yourself honestly whether this is the right path for you. Agile projects are far from the only kind out there, and sitting in the team feeling frustrated doesn’t help anyone.
With automation, the concept and the subject matter are much easier to learn and fold into daily work. One big pitfall is the complexity of the test object and of the automation tool or framework. The devil is in the details. I consider a meaningful proof of concept, and a decision and implementation made as a team, to be key. But what I sometimes miss most is the courage to abandon the chosen path when you hit major obstacles, and perhaps try other approaches to automation. If an approach isn’t getting you anywhere, pouring more energy into it won’t help much. Likewise, it’s fine to use several tools and frameworks side by side if one isn’t enough. In my opinion, teams often react far too late here. They get stuck in the existing concept and lose valuable time instead of looking at a better-suited alternative. Frustration goes up instead of test coverage. For test automation to take off, it needs a lot of attention, from planning all the way to maintenance.
Is It True That Agile Gives Testers More Influence, or More Power?
By their structure, agile projects focus more strongly on quality, with all team members sharing responsibility for it. A lack of quality also shows up much faster in an agile environment. So the basic condition for testers being heard in the team is more likely to be met than in traditional project structures. What matters is what people make of it. There are traditionally run projects that live quality to the fullest, and there are agile projects that fail because quality isn’t carried by everyone on the team.
Do Creativity and Testing Go Together?
Absolutely! Creativity is becoming more and more important for testers, and that’s a very good thing. To me, it shows that some quality-boosting practices (pushed along by agile in particular) are working: developers are writing more unit tests and using TDD, for example. In many cases, that hardens the software and makes it more stable. Code reviews are done more conscientiously. Support from development and test frameworks keeps improving. Test automation becomes an integral part of development. All of this takes load off the tester, who can turn their attention to more important things: designing good tests and questioning the product from the user’s point of view. Both call for more creativity and new skills.
How Do You Think Software Testing Will Develop over the Next Few Years?
In my view, three shifts will shape software testing more strongly in the coming years:
- New “playing fields” for software testing will open up, much like mobile app testing did. A whole range of new device classes is getting ready to launch. Smart homes, 3D printing, self-driving cars, drones, the Internet of Things: there’s a lot of software out there waiting to be tested. That means adapting test methods and building new test frameworks, among other things.
- Quality will become even more of a core task for the entire project team. The classic tester who keeps preaching quality like a broken record and acts as the sole “quality controller” will lose importance.
- Software testing will have to focus even more on what users need. User experience, usability and intuitive operation will carry more weight than the formal verification of implemented requirements.
What Skills Will Testers Need in the Future?
To be ready for these developments, I would highlight the following skills, and I try to build them up in my teams:
- Creativity in designing tests that deliver real value
- Consulting skills to support other team members (developers, etc.)
- Being a “user whisperer” who can speak for users and their behavior
- Technical understanding of how to use test (automation) frameworks
Frequently Asked Questions
Why do some testers find it difficult to transition from a traditional project to an agile one?
Because agile work is more than just a different process. Some testers are naturally enthusiastic about the new possibilities, while others feel lost because they don’t quite understand the approach. It’s helpful to explore the values, concepts, and motivation behind the agile approach, along with the question of how your own skills can enhance value and quality in the project, even in unconventional ways, if necessary.
Is a certification sufficient preparation for testing in agile teams?
No. In 2015, certifications like the Certified Agile Tester were considered a recommended foundation for understanding the methodology, but they couldn’t address specific situations and problems encountered in everyday work. Anyone who finds themselves stuck after the training should honestly assess whether the agile approach is the right fit for them. Agile projects are by no means the only type of project, and frustration within the team benefits no one.
What are the most common reasons for the failure of test automation in practice?
The complexity of the test object and the automation tool: The devil is in the details. Often, teams react too late. They get bogged down in the existing concept, pour more and more energy into an approach that isn’t effective, and waste time instead of exploring a more suitable alternative. Instead of increasing test coverage, frustration then rises.
Should you commit to a single tool for test automation?
Not necessarily. Multiple tools and frameworks can be used in parallel if one alone isn’t sufficient. A meaningful proof of concept should precede any decision, and both selection and implementation are the team’s responsibility. It’s important to have the courage to abandon a chosen path when faced with major obstacles and to pursue other approaches to automation.
Does good software quality depend on the chosen process model?
No. Agile projects are structurally more focused on quality, with all team members sharing responsibility, and quality issues become apparent more quickly. What matters most, however, is what is done with that information. There are traditionally managed projects that exemplify quality, and equally, there are agile projects that fail because quality isn’t supported by everyone on the team.
Will testers become obsolete if developers use more unit tests and TDD?
No, their work will simply shift. More unit tests, TDD, more thorough code reviews, better frameworks, and test automation as an integral part of development make the software more robust and lighten the tester’s load. This allows the tester to focus on what’s more important: designing good tests and scrutinizing the product from the user’s perspective. Both of these tasks require more creativity and new skills.
Is the tester losing importance as the sole quality control officer?
In 2015, the article predicted that quality would become even more of a responsibility for the entire project team, and that the traditional tester, who constantly harps on quality and acts as the sole quality control officer, would lose importance. At the same time, new areas of application were identified: smart homes, 3D printing, self-driving cars, drones, and the Internet of Things, all requiring adapted testing methods and new testing frameworks.
What skills, besides testing knowledge, does a tester need?
In addition to creativity in designing tests that add value, the 2015 article identified three other skills: consulting skills to support other team members such as developers; the role of the “user advocate,” who can represent the user and their behavior; and technical understanding of how to use testing and automation frameworks. User experience and usability should be given greater weight than the formal verification of requirements.
