Smoke, Retest and Regression: Promo Code
Smoke testing, retesting, new feature testing, and regression testing on adding a discount promo code to a payment form.
Your first day on the team
Hi! What’s your name?
Hi! Welcome aboard!
Get to know the product
Here is our product — the order payment form of our online store. Take a good look: the customer chooses a payment method and pays for the order. Feel free to click around — this is a test environment, and no real money is charged.
Once you’ve had a look, I have your first task.
One moment, I’ll take a look.
All clear, let’s move on
Let’s quickly check that you’re ready to get started with the team. What is our product about?
Take another look at the form and try again.
That’s right! Which payment methods do we currently support?
Take another look at the form and try again.
I’m listening!
Soon we’ll add a discount promo code to the payment form. Before we change anything, we need a regression set — a list of what already works and will have to be rechecked after the change. That’s your first task.
Define the regression set
The team is about to add a discount promo code to the payment form. For now the form has no promo code, and the order can be paid in four ways.
Choose the existing payment methods that will need to be checked after the promo code is added.
This is only preparation — you don’t need to run the checks yet.
Get the task from the product manager
Hi everyone! Next month marketing is launching a newsletter with promo codes, so in the coming week we will add a discount promo code field to the payment form.
Here is how it should work: the customer enters a code in the “Promo code” field and clicks “Apply”. For testing we have the code SALE10 — it gives 10% off, and the amount due should update right away: €49.90 → €44.91.
If the code is wrong, we show “Promo code not found” and the amount stays the same. When paying with a discount, we charge the reduced amount.
For now the payment service runs in sandbox mode: instead of a real payment, a mock opens and no real money is charged. That’s OK for testing.
Mark is taking the development, and testing is on you. If you have any questions about the requirements, message me.
Hi Mari! Could you please draw the design based on Krista’s requirements?
Mari is working on the design
Hi! Attaching the mockup: the promo code field goes below the payment methods, and once applied, the amount is shown with the discount. The payment methods stay the same.
I have looked at the requirements and the mockup — everything seems clear. Shall I start working?
Yes, go ahead
Mark is working on the task
Hi! The promo code is added, and the new build 0.12 is already on the test environment. You can start testing!
Run a smoke test
Quickly check whether the new build is ready for further testing: the form opens, the amount due is shown, the payment button is available.
Check the fix
Mark, the smoke test of build 0.12 failed. As soon as the form opens, the amount due shows “€NaN”, and the “Pay” button is disabled — the order cannot be paid even without a promo code. There is no point in checking the promo code and payment methods further, so I’ve stopped testing. I’ve filed bug report and attached a screenshot.
Thanks for the bug report! I found the cause: when the promo code field was empty, the amount was calculated incorrectly. I fixed it, and build 0.12.1 is on the test environment — please check.
Make sure the amount due is shown correctly (€49.90) and the “Pay” button can be clicked.
Click “Pay” in the form to check the button.
Look at the form again: the amount due is shown correctly, and the “Pay” button can be clicked. The defect you found during the smoke test is fixed.
This is a retest: checking a specific defect again after it has been fixed.
Now finish a short smoke test
Test the new feature — promo code
Hi everyone! Next month marketing is launching a newsletter with promo codes, so in the coming week we will add a discount promo code field to the payment form.
Here is how it should work: the customer enters a code in the “Promo code” field and clicks “Apply”. For testing we have the code SALE10 — it gives 10% off, and the amount due should update right away: €49.90 → €44.91.
If the code is wrong, we show “Promo code not found” and the amount stays the same. When paying with a discount, we charge the reduced amount.
For now the payment service runs in sandbox mode: instead of a real payment, a mock opens and no real money is charged. That’s OK for testing.
Mark is taking the development, and testing is on you. If you have any questions about the requirements, message me.
Check the promo code against the PM’s requirement. You can tick a check only after you have run it in the form.
- Run this check in the form first
- Run this check in the form first
- Run this check in the form first
- Run this check in the form first
Run the regression tests
The promo code works. Now check that without a promo code every payment method still charges the full amount — €49.90.
Regression set from the first step:
- Run this check in the form first
- Run this check in the form first
- Run this check in the form first
- Run this check in the form first
This payment went through with the discount. For regression, pay without a promo code — click “New order”.
Make the release decision
All checks are done. Is build 0.12.1 ready for release?
Krista, testing of build 0.12.1 is complete. The smoke test defect is fixed, the promo code works as required, and regression has passed. There are no open defects — the build is ready for release.
Super, great! Let’s release.
Krista has given the go-ahead. Shall I deploy build 0.12.1 to production?
Yes, deploy it
Mark is deploying the release
Done! Build 0.12.1 is in production.
Hi everyone! The discount promo code is now live in production — marketing can launch the newsletter.
Testing complete!
- Smoke — checked that the build was ready for testing.
- Retest — checked the fix for a specific defect.
- New feature testing — checked the discount promo code.
- Regression — checked that payment without a promo code works as before.
- Release — decided that the build is ready for release.
Amount due: €49.90
Payment service mock
Order paid
Quick reference
Smoke testing
A short check of the most important functions of a new build: does the application open, do the key elements work. If the smoke test fails, the build goes back to the developer — further testing makes no sense.
Retesting
Checking a specific defect again after it has been fixed: you repeat the steps that reproduced it and make sure the defect is gone.
New feature testing
Checking that a new feature works according to the requirements: the main scenario, alternative scenarios, and error handling.
Regression testing
Checking that the changes have not broken what already worked. It helps to define the regression set in advance — before work on the new feature starts.