Automation Testing CI/CD and DevOps Integration

Question 1

What does CI stand for in a CI/CD pipeline for test automation?

Accepted Answer

Continuous Integration

Answer

CI stands for Continuous Integration, the practice of automatically building and testing code every time a change is committed.

Question 2

Which Jenkins file type defines a pipeline as code using Groovy syntax?

Accepted Answer

Jenkinsfile

Answer

A Jenkinsfile defines the entire Jenkins pipeline as code using declarative or scripted Groovy DSL, stored in version control.

Question 3

In GitHub Actions, what triggers an automated test workflow on every pull request?

Accepted Answer

on: pull_request event in the workflow YAML

Answer

Adding `on: pull_request` in the GitHub Actions workflow YAML file triggers the workflow whenever a pull request is opened or updated.

Question 4

What is the purpose of a build artifact in a CI/CD pipeline?

Accepted Answer

A file produced by the build process (like test reports or binaries) that can be stored and passed between stages

Answer

Build artifacts are outputs (compiled code, test reports, packages) that are archived after a CI stage and can be used in subsequent pipeline stages.

Question 5

What does 'shift-left testing' mean in a DevOps context?

Accepted Answer

Running tests earlier in the development lifecycle

Answer

Shift-left testing moves testing activities earlier (to the left on a timeline) in the software development lifecycle to catch defects sooner.

Automation Testing Practice Test