Why Jenkins?
Jenkins automates test execution and build deliveries so QA work runs on schedule or when code changes, without manual execution.
Build process
A Jenkins pipeline typically checks out a repo, installs dependencies, runs Maven tests, and publishes test artifacts or reports.
pipeline {
agent any
stages {
stage('Checkout') {
steps { git url: 'your-repo-url.git' }
}
stage('Build + Test') {
steps { bat 'mvn clean test' }
}
}
}
Update the git URL to point to your local automation repository or internal Git host.
Repository setup
Keep Jenkins configuration inside your automation project, including pipeline scripts, test commands, and report generation.
Use local project branches and internal Git repositories instead of external document links.
Key benefits
Scheduled runs
Run tests automatically on every commit or at fixed intervals.
Central reports
Keep logs, screenshots, and test results in one accessible place.
CI/CD alignment
Use Jenkins as the integration point between source control and automated QA tests.