Note: Test engineers Reena Kuni and Jeannette Smith also contributed to this blog.
Everything about software has changed—how it’s architected, developed and produced, what it does, what users want from it, and how often they expect new features. To keep up, organisations are turning to continuous delivery and DevOps. Yet product teams still do a lot of manual testing, which consumes a lot of time they don’t have, thanks to shrinking test windows. Incorporating automation into your testing approach is a great strategy, but figuring out where and how to start isn’t necessarily quick and easy.
Today we are excited to bring you a guest blog post from Dr Greg Law, at Undo. TestPlant announced a technology partnership with Undo on August 17, 2016. To read more about the partnership, click here.
The rise of test-driven development, agile methodologies, continuous integration and continuous deployment are transforming how software is created and provided to customers. Simultaneously, the spread of software into more and more of the devices around us and the interconnectivity of those devices means that the sector is growing in scale, complexity and importance. These factors are having an enormous impact on testing and QA departments. If more software is being produced and needs to be deployed in shorter and shorter timeframes, traditional testing methodologies have to change, hence the rise of automation in the testing process.