Continual testing is one of the inherent hallmarks of the agile method. As a result, programmers are now required to conduct more testing as part of their job, prior to handing off to the software testers. This means that agile testers are expected to test on changing requirements and codes without having any formal requirement documents. During this time, agile testers will most likely run into a few challenges. Below we have listed these potential pitfalls along with a few suggestions for overcoming them:
1) Being excluded from team meetings
– Issue: Testers, business users and programmers will operate in silos rather than communicating throughout.
– Solution: A representative from each group should be present at all meetings to ensure that there are open lines of communication.
2) Waiting until the end of the build
– Issue: Stores are not being tested regularly, so bugs are not being uncovered in a timely manner and stakeholder feedback is not being obtained
– Solution: Test regularly and obtain programmer’s input more quickly
3) Testing manually
– Issue: Testing everything manually will lead to delays and an inability to test new features.
– Solution: Automating the tests
4) Tunnel vision
– Issue: Not looking at the big picture in terms of testing may result in building the incorrect product
– Solution: Build acceptance tests first by using test data that reflects real world scenarios, taking into account the business workflow
5) Skirting Quality
– Issue: The entire spectrum of the test team does not participate into building quality.
– Solution: Test interactions need to be increased from the beginning with developers as well as continual communication with programmers.
While these potential pitfalls may appear to be considerable, they can certainly be managed with the right approach rather than allowing your team to be intimidated by them.