ππ¦π¨π€π vs πππ§π’ππ² vs πππ π«ππ¬π¬π’π¨π§ vs πππππ¬ππ’π§π testing?
1. ππ¦π¨π€π πππ¬ππ’π§π
Smoke testing in web development involves a quick check to ensure the core functionalities of a web application are working before delving into more detailed testing.
ππππ§ππ«π’π¨:
You've just launched a new e-commerce website. Before conducting detailed tests, you quickly check if:
- The homepage loads.
- Users can log in.
- The search function works.
- Users can add items to the cart and proceed to checkout.
If any of these core features fail, you halt further testing and address the issues immediately.
2. πππ§π’ππ² πππ¬ππ’π§π
Sanity testing is a narrow and deep testing approach focusing on specific parts of the web application after minor changes or building Wishlists.
ππππ§ππ«π’π¨:
A developer fixed a bug where the 'Add to Wishlist' button wasn't working on the Wishlist page. You perform sanity testing by:
- Verifying the wishlist's Add to Wishlist button now works correctly.
- Ensuring that the wishlist updates and displays the added items.
You don't test the entire website, just the parts related to the bug fix.
3. πππ π«ππ¬π¬π’π¨π§ πππ¬ππ’π§π
Regression testing ensures that recent changes or updates to the web application haven’t adversely affected existing functionalities. It involves re-running previously conducted tests to confirm everything still works as intended.
ππππ§ππ«π’π¨:
Your team added a new feature allowing users to filter products by color. To ensure this new feature didn't break anything, you conduct regression testing:
- Check if the login process still works.
- Verify the search function and cart functionality.
- Ensure the checkout process and payment gateway are still operational.
- Test previously fixed bugs to ensure they haven't resurfaced.
4. πππππ¬ππ’π§π
Retesting focuses on verifying that specific defects have been fixed. Unlike regression testing, it centers on the failed test cases that have been corrected.
ππππ§ππ«π’π¨:
There was a bug where the contact form on the website wasn't submitted properly. After the development team fixes it, you perform retesting by:
- Submitting the contact form to ensure it works correctly now.
- Checking if the form submission sends an email notification as expected.
You don't check other parts of the website, just the specific issue that was fixed.
