How can you reduce risk when implementing agile development in your SDLC?
In a recent post on DevOps.com entitled, “Get Testing Bottlenecks Out of Your Pipelines,” Lisa Crispin drives the point home regarding the importance of manual testing steps in the deployment pipeline.
“I think a lot of times people forget about these important manual stages… Though we can do more and more with test automation, thanks to improving technology, manual testing activities are here to stay in most business domains.”
We couldn’t agree more. Today, there is a hard push toward testing automation because manual testing, historically, hasn’t been known to be the most agile process. Testing automation can be a real timesaver since you can integrate it into your software development life cycle and initiate tests on a continuous basis.
But even with 95 percent test coverage:
If you’re ready to supplement your automation or dive into a different approach to QA, your team could benefit from performing exploratory manual testing. Skeptical of focusing more on manual testing in-house? Maybe because:
As Lisa puts it...
“Manual exploratory testing is likely to take longer than the automated test suites. If user acceptance testing needs to be done by certain business stakeholders and they aren’t available at the right time, that holds up the release.”
So, how do you speed this up? According to Lisa, you can:
At test IO, we have another solution to these issues: a fusion of the automated and the manual, through access to our agile testing platform and thousands of qualified testers who can perform the tests you need on-demand. This type of speed and efficiency eliminates those bottlenecks associated with manual testing while providing your QA team and developers with detailed bug reports, usability feedback, and bolstered confidence in your testing processes.
We take the principles of manual testing and mesh them with the practices of automation:
Across the board, the goal is clear. As Lisa suggests...
“Automate all the things where it’s feasible. Use the time you save to optimize the way you accomplish manual testing activities and possibly automate more of them.”