Sanity Testing

Today, we're going to discuss Sanity Testing. Can anyone explain what they think it involves?

Isn’t it about quickly checking if a fix works or not?

Exactly! Sanity Testing is a quick check to ensure that a recent bug fix or functionality works as expected. Think of it as a sanity check for the software.

So, it’s only about one specific issue?

Yes! It's focused rather than comprehensive. If a bug is fixed in the cart, we test that specific flow without looking at unrelated areas.

Why is it important to do this?

Great question! It helps us ensure that fixes are valid before we spend time on more extensive testing. It’s like a preliminary assessment.

In short, Sanity Testing is essential for maintaining software quality. Remember: It's all about checking that the specific function remains functional after changes.

Now that we’ve covered the basics, what do you think would be included in a typical Sanity Test?

Would it involve just rerunning the test cases associated with the bug?

Yes! Those specific test cases are executed again to validate the fix. Who can think of an example?

If there was a bug in the checkout process, I imagine we'd only test that instead of the whole system.

Exactly! Sanity Tests save time by narrowing down the focus to affected areas, allowing us to quickly confirm functionality.

Would this be done before every deeper testing phase?

Yes! It serves as a checkpoint. If Sanity Tests pass, it indicates that we can cautiously proceed with more detailed testing.

To summarize, always remember that Sanity Testing is your initial line of defense against regressions in modified functionalities.

Now, let’s compare Sanity Testing and Smoke Testing. Can someone distinguish them for us?

I think Smoke Testing checks general stability, while Sanity Testing is more focused?

Correct! Smoke Testing checks basic functionalities, ensuring critical systems work, like login and homepage load. Whereas Sanity Testing digs into recent changes only.

So, we use both, but at different stages?

Precisely! Smoke Testing is typically done after a new build, while Sanity Testing follows specific bug fixes. Anyone want to offer an example to illustrate this?

If we deployed a new version, Smoke Testing checks the app starts up. If a specific bug was fixed afterward, we’d do Sanity Testing on that fix.

Exactly! This comparison helps clarify the purpose of both, supporting the overall testing strategy. Great discussion, everyone!