Learning path recommendations after getting started with Cover Pipeline for GitLab
Once you're familiar with the topics covered under Cover Pipeline for GitLab, check out the following to help extend your unit test capabilities even further:
Specs & Reqs
Specifications, prerequisites, and general project requirements are all covered in Specs & Reqs.
dcover Commands in a pipeline
Additional optional arguments can be used with the create and validate commands listed in your .gitlab-ci.yml file for your project - see Commands & Arguments for details. Note that Cover Reports arguments are not currently supported for use with Cover Pipeline for GitLab.
Diffblue Cover performs a number of checks before, during, and after creating unit tests. Cover can generate a range of output codes during these checks to provide general information and highlight any issues. These codes and associated messages are output during the run, visible in the job output, and saved to the log files. See Output Codes for details.
See the Code Coverage topic for general information on ways to improve your overall coverage across your Java projects.
Diffblue Cover is also available as two developer tools - Cover Plugin for IntelliJ (write tests directly within the IntelliJ IDE) and Cover CLI (full command line tool) - both of which are bundled with Cover Pipeline for GitLab. These tools can be used by your development staff to automatically write tests during the development stages of a project, thereby allowing them to check for regressions and unplanned code behavior changes even before the code is committed back to GitLab. See the Free trial or Beyond the trial - get started topics to check out the tools for yourself.