Testing a Shop Update is a practical Jenkins project for learners who have run a basic Pipeline and want its test results to control a real release. Work with Moss & Mallow, a fictional gift shop whose prices, basket estimates and downloadable care card actually work.
One Guided Lab follows an incorrect candidate from a real failed pricing test to an unexpected publication. You then repair the gate and deliver a working candidate. One independent Challenge applies the same methods to a delivery-fee update in a fresh environment.
What You Will Learn
After completing this course, you will be able to:
- read a Jenkins pricing-test failure and relate it to the customer-facing result;
- distinguish a test-script exit status, a published JUnit report and the overall build result;
- prevent later publication after an unstable test result without hiding the failure details;
- prove the same saved Pipeline rejects a broken candidate and publishes a working candidate;
- download a build artifact and verify the live prices, normal pages and download remain correct.
Who This Course Is For
This course is for beginning Jenkins users, developers and DevOps learners who want a small, complete release task.
Prerequisites: Basic Jenkins navigation and the ability to recognize a short Declarative Pipeline. Complete the Pipeline introduction in Jenkins for Beginners first if these are new. No application programming or test-framework development is required; the new report and gate settings are explained before use.
Learning environment: Each activity provides a Jenkins controller running in Docker, prepared pricing candidates and real tests, and the Gift Shop website. Use the Jenkins and Gift Shop browser entries. No cloud account, public Git service, local installation or real purchase is required. The website, interface labels and program output remain English; the learning documents are available in nine languages.
Frequently Asked Questions
Will I write the shop or its tests?
No. The application, pricing tests and publisher are provided. You change a short Pipeline and use the real results to control publication.
Why can a build with failed tests still publish?
A test report can mark a build unstable while later stages continue. The project lets you observe that behavior, connect it to a release decision and preserve the useful failure details.
How does the Challenge differ from the Guided Lab?
The Challenge changes the pricing boundary and the initial Pipeline configuration. It asks for the same tested release outcome with less guidance, and includes a complete separate solution. Every activity starts independently.
Does this cover production deployment architecture?
No. This is a local, synthetic shop and a focused Jenkins release-gate exercise. It does not take payments or configure a production deployment platform.
Cover mascot adapted with AI from artwork by the Jenkins project, under CC BY-SA 3.0.
