CartSure Build Verification, Sanity & UAT Phase

Welcome!

You are now performing Build Verification, Sanity Testing, and UAT Testing in the CartSure project as a Software Tester.

Before testing newly developed features in real-world applications, it is important to verify whether the application build is stable enough for detailed testing activities.

This helps ensure that major functionalities are working correctly before moving to advanced testing phases.

So, today you will learn how to perform Smoke Testing, perform Sanity Testing, understand User Acceptance Testing concepts, and validate business requirements in the CartSure project.

Topic: Testing Types

1)Functional vs Non-Functional
2)Smoke, Sanity, Regression
3)Alpha, Beta, Acceptance Testing
4)System, Integration Testing

Open the CartSure website

Test basic functions:

• Log in with a valid user.

• Search for a product.

• Add product to cart.

• Checkout and payment.

Record results.

Example: Login works, product added to cart, and payment succeeds → Build is stable.

Identify areas that have changed in the new build (e.g., Add to Cart bug fixed).

Test only the modified areas.

Confirm that the fixes work and that no new issues appear.

Example: Add to Cart button fixed → Test adding multiple products, check cart updates correctly.

Review business requirements (BRD).

Test key workflows:

• Apply coupon codes.

• Calculate discounts.

• Generate order confirmation email.

Note any discrepancies.

Example: Coupon 10% off applies correctly → Requirement satisfied.

Prepare UAT scenarios based on real user actions.

End users test workflows: login → search → add to cart → checkout → receive confirmation.

Example: User completes purchase successfully and receives order confirmation email → UAT passed.

Record feedback and defects.

Ensure all UAT defects are fixed before production

OUTPUT: UAT validation report

Great job!

You have successfully completed your CartSure Build Verification, Sanity & UAT Phase session.

Applied Smoke Testing, Sanity Testing, and User Acceptance Testing (UAT) to verify build stability, validate critical functionalities, and ensure business requirements were successfully met before release.

You now understand how testers verify build stability, validate important functionalities, and ensure business requirements are satisfied before production release.

Topic: Working with a Text and Listing HTML
Introduction to Bugasura
Test Case Management
1) Creating Requirements
2) Creating Test Cases
3) Executing Test Case
4) Defect Logging with Defect Management