Skip to main content

Sanity Testing

Sanity Testing is perform when QA team received the build after fixes of minor bugs or some new functionality added. In Sanity Testing, QA team check that the bugs that generated in last build should be fix and due to those bug fixes there should be no new bugs generated. So in Sanity Testing first QA team check the regression testing and after regression testing QA team verify the previous bugs.



The Goal of Sanity Testing is to check that the software should meet the client expectation. Sanity Testing is very cost effective. if Sanity Test fail then revert the build to the developer team which save lots of time.

The Objective of Sanity Testing is not to verify thoroughly the new functionality of the software.

Sanity Testing always perform when the software PASS in the Smoke Testing. Sanity Testing is the narrow regression testing which focus on new area of the software. Sanity Testing is narrow and deep.

Sanity testing perform after lots of regression testing is already performed and come now for minor changes in build. In this cases we perform the deep testing of functionality for these changes.  Sanity testing is the Sub Regression Testing

Comments

Popular posts from this blog

Why Jmeter is best option for Performance Testing?

There are multiple tools in market for performance testing of any software but Jmeter is the best solution among all of them due to some reason listed below 1) Jmeter is the open source application so users who use this application will not to pay anything. 2) You can use Jmeter for performance of any web application,  Databases and Web Services (REST and SOAP APIs). 3) Jmeter have the user friendly UI component so it is very easy to use. 4) Jmeter can be used to simulate to put maximum number of concurrent users on a server, network or object to test its strength or to analyze overall performance under different load types. 5) Jmeter also use for functional testing for static( JavaScript and HTML) and dynamic( JSP, Servlets and AJAX) resources. 6) Jmeter provides Verity of graphical representations for performance report so it is easy to understand.

How You Can Test Database?

Now we know the Database Testing which you can learn in my last article. In this article we will discuss about the steps that need to following to test any Database. Database Tester should have some basic knowledge regarding SQL Command like DDL (create/drop),  DML (Insert/Delete/Update) and DCL (Grant/Revoke).

Causes of Software Defects

It is practically impossible that developer develop a bug free software and that software we can deliver without Testing. If the complexity of the software increased then there must be bugs that can harm the users who will use that software.