How do you keep track of all the moving parts of Continuous Testing?
Source Code, Test Scripts, logs, visuals, and other artifacts are created and collected during the all-encompassing processes of Continuous Testing throughout the DevOps pipeline. The amount of test data and number of artifacts are constantly growing and at the same time require traceability. We at Perfecto, see digital enterprises asking a key, fundamental question: How do we optimize testing activities in order to identify and fix issues as early as possible in the SDLC?
The era of ‘Continuous EVERYTHING’ places more demands on DevOps teams who are required not only to widen the scope of their tests but also execute tests more often. Developers spend precious time chasing after the right code version, correlating and manually searching for the differentiation (between versions) in order to ‘put their finger’ on the root cause which, potentially, failed. Searching for code issues (a.k.a needles in the haystack) requires the expensive resource of TIME.
Following validation activities and discussions with DevOps teams, frustrated with a complex root-cause analysis process, Perfecto identified that organizations need to increase efficiency when it comes to Version Control software integration. With DigitalZoom™ Analytics platform, users can ensure that each and every test execution is tied to the relevant commit and source code file in their VCS, thereby accelerating the root-cause analysis process.
Using the Custom Field contextual layer of the DigitalZoom™ SDK, a user can specify a set of identifiers in the VCS and Commit, that optimize links for fast access for analysis/fix activities.
This new feature has built-in integration with GitHub, GitLab and Bitbucket.
To learn more about this functionality, please see the following article on Perfecto’s Developers site.