GitLab workflow

Illustrative development workflow, with and without Cover Pipeline for GitLab

Integrating Diffblue Cover into your CI/CD pipeline supports the software development workflow to provide AI automation of unit tests. The following provides an illustrative development workflow, with and without Cover Pipeline for GitLab, covering key steps to illustrate differences in workflow.

Without Cover Pipeline for GitLab	With Cover Pipeline for GitLab
A Java project with manually written tests.	A Java project with an AI created Java Unit Test Suite.
A software developer makes a code change and manually updates the associated unit tests.	A software developer makes a code change - no manual unit test update is needed.
After a merge request, the code change and unit test change are manually reviewed.	After a merge request, the Diffblue Test Suite is automatically updated, and the code change and unit test change are reviewed. The test diff assists with catching regressions and bugs.
After passing code review, the updated code and associated unit tests are merged.	After passing code review, the updated code and associated unit tests are merged.