How do we keep on top of regression testing.
The DevOps model allows multiple developers to check in their changes with new builds being created daily (or more often). Any issues with code are highlighted quickly, but how do we keep on top of the regression testing?
What if we could capture any changes as soon as the build is complete?
Using Original Softwareâs Jenkins integration, thatâs how!
Jenkins* is the perfect tool to automate the process; itâs free and open-source. It has an array of plugins, is simple to install and manage, and is the go-to tool for controlling your builds. And if you are using TFS or another tool, it will have a plugin and integrate. TestDrive from Original Software enables code-free test automation without specialist programmers and uses patented AI to adapt to change and minimize maintenance.
Having built your regression pack in TestDrive you can utilize these assets within Jenkins. Once the developerâs code has been checked in and a build deployed, the TestDrive plugin will allow the regression pack to be run on your test server. Once completed, the results can quickly be made available via email, team message, SMS message, or by utilizing any of the Jenkins plugins.
Integrating TestDrive with Jenkins, you can run full regression test automation with every significant change checked automatically with every new build, and you can find issues and changes quickly, allowing fast, trouble-free deployment of your application.
Justin McDougall is a Training and Implementation consultant at Original Software
*The leading open-source automation server, Jenkins provides hundreds of plugins to support building, deploying, and automating any project.
