Integration test stages in Jenkins - Step-by-Step Execution

Process Flow - Integration test stages

Start Pipeline

↓

Checkout Code

↓

Build Application

↓

Run Unit Tests

↓

Run Integration Tests

↓

Publish Test Results

↓

Deploy or Notify

↓

End

This flow shows the main stages of a Jenkins pipeline running integration tests after building and unit testing the application.

Execution Sample

Jenkins

pipeline {
  agent any
  stages {
    stage('Integration Test') {
      steps {
        sh 'run-integration-tests.sh'
      }
    }
  }
}

This Jenkins pipeline stage runs integration tests by executing a shell script.

Process Table

Step	Stage	Action	Result	Next Step
1	Start Pipeline	Initialize Jenkins job	Job started	Checkout Code
2	Checkout Code	Pull code from repository	Code available locally	Build Application
3	Build Application	Compile and package app	Build successful	Run Unit Tests
4	Run Unit Tests	Execute unit tests	All unit tests passed	Run Integration Tests
5	Run Integration Tests	Execute integration tests script	Integration tests passed	Publish Test Results
6	Publish Test Results	Archive and display test reports	Reports published	Deploy or Notify
7	Deploy or Notify	Deploy app or send notifications	Deployment done or notified	End
8	End	Pipeline finished	Success	None

💡 Pipeline ends after deployment or notification stage completes successfully.

Status Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	After 6	Final
pipeline_status	Not started	Started	Code checked out	Built	Unit tests passed	Integration tests passed	Results published	Deployed/Notified
integration_test_result	Not run	Not run	Not run	Not run	Not run	Passed	Passed	Passed

Key Moments - 2 Insights

Why do integration tests run after unit tests and not before?

Integration tests depend on the application being built and unit tests passing first, as shown in execution_table rows 4 and 5 where unit tests pass before integration tests run.

What happens if integration tests fail during the pipeline?

If integration tests fail, the pipeline stops before publishing results or deployment, preventing broken code from progressing, as implied by the flow stopping after step 5 if tests fail.

Visual Quiz - 3 Questions

Look at the execution table, what is the pipeline_status after step 4?

A Built

B Integration tests passed

C Unit tests passed

D Code checked out

💡 Hint

Check variable_tracker row for pipeline_status at After 4 column.

At which step does the integration test script run?

A Step 3

B Step 5

C Step 4

D Step 6

💡 Hint

Look at execution_table Stage and Action columns for running integration tests.

If integration tests fail, what is the likely next step in the pipeline?

A Pipeline stops

B Deploy or Notify

C Publish Test Results

D Run Unit Tests again

💡 Hint

Refer to key_moments explanation about pipeline stopping on test failure.

Concept Snapshot

Jenkins pipeline stages for integration tests:
- Checkout code
- Build application
- Run unit tests
- Run integration tests
- Publish results
- Deploy or notify
Integration tests run after unit tests and build succeed.

Full Transcript

This visual execution shows a Jenkins pipeline running integration tests. The pipeline starts by checking out code, building the app, and running unit tests. If unit tests pass, it runs integration tests by executing a shell script. After integration tests pass, it publishes test results and then deploys the app or sends notifications. Variables like pipeline_status and integration_test_result update at each stage. If integration tests fail, the pipeline stops to prevent faulty code from deploying.