NetStorm – Test Suite
This section provides implementation details of the process involved in the execution of continuous delivery using NetStorm and software like Jenkins. The whole process is explained under heads of “NetStorm Continuous Delivery configuration”, “Continuous delivery test execution” and description of test report generated after the execution.
What is Continuous Delivery
Continuous Delivery (CD) is a design practice used in software development to automate and improve the process of software delivery. Techniques such as automated testing, continuous integration and continuous deployment allow software to be developed to a high standard and easily packaged and deployed to test environments, resulting in the ability to rapidly, reliably and repeatedly push out enhancements and bug fixes to customers at low risk and with minimal manual overhead.
NetStorm is integrated with different tools for the enterprise implementation of Continuous delivery. While test execution occurs on NetStorm, monitoring is done by CavMon agent on server. Additionally, NetDiagnostics can also be deployed on the server for deeper digging at application code level. The diagram below shows the complete architecture and work flow of the Continuous delivery process using NetStorm.
Jenkins triggers a Test Suite (created on the NetStorm) and in parallel, NetStorm captures the Performance Metrics with the help of CavMon Agent running on the servers. It has SLAs configured, based on which, the test is either Passed (If SLA met) or Failed (If SLA not met). TestSuite automates the execution of tests and displays CICD reports based on configured rules.
Jenkins finally contains the basic details of the test executed and a link to the brief report of the test.