Testing shared libraries in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of a Jenkins shared library test script

Given this Jenkins pipeline snippet that calls a shared library function, what will be the output in the Jenkins console log?

Jenkins

library('my-shared-lib')
node {
  stage('Test') {
    echo mySharedFunction('hello')
  }
}

// Assume mySharedFunction is defined in vars/mySharedFunction.groovy as:
// def call(String input) { return "Processed: ${input}" }

A Processed: hello

B hello

C Error: No such method 'mySharedFunction'

D mySharedFunction(hello)

💡 Hint

Remember that shared library functions defined in vars can be called like normal functions in the pipeline.

The shared library function 'mySharedFunction' defined in vars returns the string 'Processed: ' plus the input. So calling it with 'hello' outputs 'Processed: hello'.

🧠 Conceptual

intermediate

Purpose of unit testing Jenkins shared libraries

Why is it important to write unit tests for Jenkins shared libraries before using them in pipelines?

A To reduce the size of the shared library code

B To speed up Jenkins pipeline execution time

C To automatically deploy the shared library to production

D To verify the shared library functions behave correctly and avoid pipeline failures

💡 Hint

Think about the risks of using untested code in automation pipelines.

Unit tests help catch bugs early in shared library code, preventing pipeline failures and improving reliability.

❓ Troubleshoot

advanced

Troubleshooting missing shared library in Jenkins pipeline

A Jenkins pipeline fails with the error: 'No such library found: my-shared-lib'. What is the most likely cause?

A The pipeline script syntax is incorrect

B The shared library 'my-shared-lib' is not configured in Jenkins global settings

C The Jenkins agent node is offline

D The shared library code has a syntax error

💡 Hint

Check Jenkins global configuration for shared libraries.

If Jenkins cannot find the shared library, it usually means it was not added in the global configuration under 'Configure System' > 'Global Pipeline Libraries'.

🔀 Workflow

advanced

Correct order to test a Jenkins shared library locally

What is the correct sequence of steps to test a Jenkins shared library locally before pushing it to the central repository?

A 4,3,2,1

B 3,4,1,2

C 1,2,3,4

D 2,1,4,3

💡 Hint

Start by writing and running tests before integrating with Jenkins pipelines.

First write unit tests, then run and fix them locally. Next, create a Jenkinsfile to call the library, and finally run the pipeline in a local Jenkins environment.

✅ Best Practice

expert

Best practice for mocking Jenkins steps in shared library unit tests

When unit testing Jenkins shared library functions that call Jenkins pipeline steps like 'sh' or 'echo', what is the best practice to handle these calls?

A Mock the Jenkins pipeline steps to simulate their behavior without running them

B Run the actual Jenkins pipeline steps during unit tests

C Remove all pipeline steps from the shared library code before testing

D Ignore pipeline steps and test only pure Groovy code

💡 Hint

Think about how to isolate your code from Jenkins runtime during tests.

Mocking pipeline steps allows testing shared library logic without needing a Jenkins runtime, making tests faster and more reliable.