Difference Between Smoke and Sanity Testing

Smoke and Sanity Testing

In general Smoke and Sanity testing seems very similar to many tester who have just started, because in both we talk about build, we talk about functionality and we talk about the rejection of builds if build’s health is not well for the feasible testing.

After going through several project from start ups to product base company, I come to figure-out the basic difference between Smoke and Sanity testing.  I am writing difference between smoke testing and sanity testing here to help you in answering at least one question that normally all testers get asked in interview.

Smoke testing :

smoke testing is done to test the health of builds

– it is also know as the shallow and wide testing in this we normally include those test case which can cover all the functionality of product

smoke testing, we can say that is the first step of testing and after this we normally do the other kind of functional and system testing including regression testing

Smoke testing is normally done by Developer with the help of certain script or certain tools in some cases it is done by Tester too

– One more thing,Smoke testing is valid for initial stage of build confirmation like we have started development of certain product  and we are producing build for the first time then Smoke testing become necessity for the product.

Sanity Testing :

– It is sub-regression
Sanity is done for those builds which have gone through many regression and has come after a minor change in code. In this case we normally do the intensive testing of functionality for which this new change has come.
– Due to this it is also know by narrow and deep testing
Sanity is done by Tester
Sanity is done for mature builds like build those are just going to hit production and have gone though multiple regression process.
Sanity can be removed from the testing process if regression is in process of testing.
– IF any build doesn’t pass sanity testing, then it is thrown to developer back for the correction in build.

Since the very start of this article i am speaking build, build and builds and there will be many reader who would be getting it irritating that what the hell is this BUILD. So let me  write few lines for the definition of Builds

Software Builds : A simple software is made up of multiple code files and when these files are separate its compilation seems easy but it is very tedious to compile all files before execution of an program. So developer makes executable file by combining all these files. These executable file are known by the name of Software Builds.

Hope now you would be comfortable with the testing keyword Builds

but friends if i am lagging somewhere then please do me a favor by dropping supportive comment over this topic.

Difference Between Test Case and Test Scenario

Test Case and Test Scenario

When i have started my career as Test Engineer, I was bit confuse between Test Case and Test Scenario. After a long time i come to know the basic difference between Test Case and Test Scenario, the two typical keyword of testing which are the base of whole testing. but this confusion was due to the interlinked connection between Test Scenario and Test Case. Finally I has come to know the difference between test case and Test Scenario

– Test Scenario : is a hypothetical story flow that covers all the typical and unusual workflow and situations that may occur in product. It means Scenario is just the story that covers all the expected flows of product that any end-user can follow while using the product While  Test Case: is just the conditional or a kind of variable that is given as input to test whether functionality is working fine or not. The pass and fail criteria of a test case is normally mentioned in Test Plan.

– normally test scenario is the sequence of test cases that are executed one after other while Test Case are just the single step to accomplish the task.

Test scenario ensures that all business flow has been covered and tested end to end while Test case ensure that a single step has been covered well.

– So most of the people use to say that test scenario is just the way “What to test ” and it normally speaks about functionality while Test Case say “How to Test”.

– Test Scenarios are derived from some use case while Test Cases are the integral part of Test Scenario or can say the connecting ring.

I think now you will be able to differentiate test scenario and Test Cases

Typical Test Case format<each test case template contain all the following keywords as Column>

Test Case ID

Prerequisite 

Test case Description

Test Data

Steps 

Category 

Author

Drop Down (Automated/Manual)

Expected Result

Actual Result

Pass/Fail

Remarks

Since this is generic format and this test case format varies from company to company. Since in my company we normally mention the Priority and Severity in test case format as well . So be ready and make your very first test case template at your own.  Good Luck

your opinion is expected and if i have left anything then please mention this through your comments

Software Testing Life Cycle

Since we are talking all about testing in this blog so it is very important to mention the real testing cycle that is used by tester to test the product in real scenario.

So friends, Testing is just a part of Software Development Life Cycle and is further divided in to various sub steps or we can say sub phases.

So these are the common STLC’s sub phases, But this is just the generic form of STLC because this can vary from company to company. So i am serving a very generic idea about this STLC Read more

1 44 45 46 47 48