Developer's tasks

Task 1: Checking out code

In Total Test, a developer checks a set of sources, copybooks and other components required to fulfill a specific requirement. See Pipeline-setup-for-Code-Pipeline.

Task 2: Creating and maintaining tests

In Total Test, the developer creates or modifies a set of (virtualized or non-virtualized) tests for the modified programs. To share the tests between development teams and to use them in Jenkins, the Total Test projects are stored and administered using Git. See Using-Total-Test-Unit-Test.

Important

Any Git server (for example GitHub, Bitbucket, GitLab) may be used as centralized repository server for Total Test assets.

Task 3: Promoting code

In Total Test, after the developer has finished working on the code, they promote their changes from the DEV level to QA, the next level in the application's life cycle.

Important

The Code Pipeline life cycle of the application used for these examples consists of three parallel development paths (DEV1, DEV2, and DEV3). At certain points in the implementation you will need to know the actual path of the life cycle that the developer is working in.

Task 4: Triggering a Code Pipeline webhook

In Code Pipeline, the promotion from the DEV level to the QA level in Code Pipeline automatically creates an Code Pipeline set containing all components that are part of this specific promotion. Once the promotion is complete, Code Pipeline triggers a Jenkins job that executes a series of automated steps. The Jenkins job is triggered via a webhook. The webhook also passes parameters to the Jenkins job to control the execution. For more information, see Pipeline-parameters and CES-Webhook-Configuration

Task 5: Triggering a CI pipeline job

In Jenkins, a pipeline job or build gets triggered automatically.