Smoke, Retest and Regression: Payment Form
Smoke testing, retesting, new feature testing, and regression testing on adding an instalment payment option 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 new payment method 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.
Build the regression set
The team is about to add a new method to the payment form. For now the form works with three payment methods.
Choose the existing payment methods that will need to be checked after the new method is added.
You’ll need this set later: we’ll use it to confirm nothing broke after the new method is added. You don’t need to run the checks yet.
Get the task from the product manager
Hi everyone! Customers keep asking about paying in instalments, so in the coming week we will add a new method to the payment form — Klarna.
Here is how it should work: the customer chooses Klarna among the payment methods, clicks “Pay”, and goes to the Klarna page to confirm the payment.
If the payment succeeds, we show “Order paid”. If Klarna declines the payment, we show “Payment failed” and let the customer try again.
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: this is how Klarna should look in the payment form. The other 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! Klarna is added, and the new build 1.5 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 payment methods are shown, the payment button is available.
Check the fix
Mark, the smoke test of build 1.5 failed. The payment form elements overlap each other, and the Klarna banner covers the “Pay” button, so it cannot be clicked. Without the button no payment can be tested, so I’ve stopped further testing. I’ve filed bug report and attached a screenshot.
Thanks for the bug report! I fixed the layout: the elements no longer overlap, and the “Pay” button is available again. The fixed build 1.5.1 is on the test environment — please check.
Make sure the form elements no longer overlap and the “Pay” button can be clicked.
Click “Pay” in the form to check the button.
Look at the form again: the elements no longer overlap, 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 — Klarna
Hi everyone! Customers keep asking about paying in instalments, so in the coming week we will add a new method to the payment form — Klarna.
Here is how it should work: the customer chooses Klarna among the payment methods, clicks “Pay”, and goes to the Klarna page to confirm the payment.
If the payment succeeds, we show “Order paid”. If Klarna declines the payment, we show “Payment failed” and let the customer try again.
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 Klarna 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
Klarna works. Now check that adding a new payment method has not broken the existing ones.
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
Make the release decision
All checks are done. Is build 1.5.1 ready for release?
Krista, testing of build 1.5.1 is complete. The smoke test defect is fixed, Klarna 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 1.5.1 to production?
Yes, deploy it
Mark is deploying the release
Done! Build 1.5.1 is in production.
Hi everyone! Klarna payments are now live in production — customers can pay in instalments.
Testing complete!
- Smoke — checked that the build was ready for testing.
- Retest — checked the fix for a specific defect.
- New feature testing — checked the new Klarna payment.
- Regression — checked that the existing payment methods still work.
- Release — decided that the build is ready for release.
Amount due: €49.90
Payment service mock
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.