Sanity Check (Re-test)

From Bloomex Wiki
Revision as of 08:27, 5 June 2025 by Alexey Shirin (talk | contribs) (Created page with "=== '''Sanity Testing – Basic Guide (Re-test Fixed Bugs)''' === '''What is Sanity Testing?''' Sanity testing checks that specific bugs or issues reported earlier are now fixed and working as expected. It is focused and limited in scope — not a full test cycle. The goal is to quickly verify that fixes were successful. '''How to Prepare?''' Review the list of fixed bugs from the issue tracker (e.g. Jira, Redmine). Read each bug report carefully: understand the probl...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Sanity Testing – Basic Guide (Re-test Fixed Bugs)

What is Sanity Testing?

Sanity testing checks that specific bugs or issues reported earlier are now fixed and working as expected. It is focused and limited in scope — not a full test cycle. The goal is to quickly verify that fixes were successful.

How to Prepare?

Review the list of fixed bugs from the issue tracker (e.g. Jira, Redmine). Read each bug report carefully: understand the problem, the expected fix, and the steps to reproduce. Make sure the test environment includes the new build with fixes applied.

How to Execute?

Re-run the original steps described in the bug report. Check if the issue still happens. If the problem is gone and the behavior matches the expected result — mark the issue as “Verified” or “Passed”. If the issue remains or changed — reopen it with updated info.

When to Run Sanity Tests?

  • After a new build with bug fixes
  • Before regression testing
  • As a quick check to confirm critical issues are fixed

Examples:

  • A user couldn’t reset their password before. You re-test the reset flow, and now it works — pass.
  • A checkout bug was fixed, but now it fails with a different error — reopen with details.
Retrieved from "https://wiki.necs.ca/index.php?title=Sanity_Check_(Re-test)&oldid=5270"