Prerequisites for onboarding

We recommend to start onboarding with a handful of selected projects from different teams. A project is typically an application or a repository.

The onboarding of each selected project will be driven by a named champion. A champion is responsible for making the project ready for Diffblue Cover, creating the baseline and communicating with DevOps to set up Cover in CI. This is usually a team lead or a senior engineer on a team. They may already have been involved in an earlier proof-of-concept.

To facilitate communication among yourselves and with Diffblue, you should gather the following information.

1. Projects, teams and developers.

   1. To how many projects in total are you planning to roll out in the long-term?

   2. How many teams work on these projects in total?

   3. How many developers work on these projects in total?

2. Screensharing and log files.

   1. Please confirm which of the following the champions can share during working sessions:

      1. Console output of Diffblue Cover (contains identifier names).

      2. Cover log files (details can be provided on request).

      3. Cover Reports (coverage data).

      4. Snippets of build configurations (pom.xml, build.gradle, build.xml).

      5. Snippets of source code.

   2. Please confirm which of the following the champions can provide in support requests.

      1. Cover log files (details can be provided on request).

      2. Snippets of build configurations (pom.xml, build.gradle, build.xml).

      3. Snippets of source code.

3. Software and license distribution.

   1. Please describe the process from being notified about an update by a vendor to the software being available to a user. E.g. security scans, internal app stores.

   2. Please name a contact for software and license distribution.

4. Cover Reports installation.

   1. Please name a contact for installing the Cover Reports web-app so that it is accessible to all the teams.

5. Diffblue recommends to start onboarding with a handful of selected projects (3-5) from different teams. For each project, the following information should be provided.

   1. Name of the project.

   2. Name of the corresponding champion contact for each project.

   3. Name of the champion’s team and the team’s location in the organization hierarchy.

   4. SCM system (e.g. GitHub) of the project.

   5. CI system (e.g. Jenkins) of the project.

   6. Build System used by the project (e.g. Maven)

   7. Java version of the project.

   8. Operating system used by champion (e.g. Windows).

   9. IDE used by champion (e.g. IntelliJ).

   10. RAM (e.g. 16GB) and number of cores (e.g. 4) of the champion's workstation.

Once the information 1-5 has been received, Diffblue will send the software and licenses to the contact for software and license distribution.

1. You then need to set up Cover Reports on a central server.
2. If the champions' workstations do not meet the required specfications for running Cover then it is recommended to provision sufficiently powerful VMs with a development environment set up that allows to build the selected projects and run tests.
3. Champions install Cover CLI, run preflight on the selected projects and send the log files to [e-mail] for inspection to inform the subsequent Jumpstart agenda.