Code coverage reports in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a code coverage report in Jenkins?

A code coverage report shows how much of your source code is tested by automated tests. It helps find untested parts to improve quality.

beginner

Which Jenkins plugin is commonly used to generate code coverage reports?

The 'JaCoCo' plugin is commonly used in Jenkins to collect and display Java code coverage reports.

intermediate

How do you publish a JaCoCo code coverage report in a Jenkins pipeline?

Use the 'jacoco' step in your Jenkinsfile after tests run, for example:

jacoco execPattern: '**/jacoco.exec'

This publishes the coverage report in Jenkins UI.

beginner

What does a high code coverage percentage mean?

It means most of your code is tested by automated tests, which usually leads to fewer bugs and better software quality.

intermediate

Can code coverage reports guarantee bug-free software?

No, code coverage shows tested code parts but does not guarantee no bugs. Tests must be well written and cover important cases.

What is the main purpose of code coverage reports in Jenkins?

A To show how much code is tested by automated tests

B To deploy code to production

C To monitor server health

D To manage user permissions

Code coverage reports help identify which parts of the code are tested, improving test completeness.

Which plugin is typically used in Jenkins for Java code coverage?

A Git plugin

B JaCoCo plugin

C Docker plugin

D Slack plugin

JaCoCo plugin collects and displays Java code coverage reports in Jenkins.

In a Jenkins pipeline, where should the code coverage step be placed?

A Before checkout

B Before running tests

C After running tests

D After deployment

Code coverage is collected after tests run to analyze which code was executed.

What does a low code coverage percentage indicate?

A Few parts of code are tested

B Most code is tested

C Tests are perfect

D Code is bug-free

Low coverage means many code parts lack automated tests.

Does 100% code coverage guarantee no bugs?

A Yes, always

B Only for small projects

C Only if tests run fast

D No, tests might miss cases

Even full coverage can't guarantee no bugs if tests don't check all scenarios.

Explain what a code coverage report is and why it is useful in Jenkins pipelines.

Think about how tests relate to code parts.

Describe how to set up and publish a JaCoCo code coverage report in a Jenkins pipeline.

Focus on the pipeline steps and plugin usage.