smoke and Sanity Testing
1. Explain differeces between Regression vs Retesting
2. Explain diffrences smoke and Sanity Testing?
3. Explain differences between verification and Validation?
4. Explain differences Functional Test and performance Test?
5. Explain differences between Load Test and Stress Test?
6. Explain differences between INT and SYS Testing?
------------------------------------------------------------------
Agenda of the Session:
Smoke Testing
Sanity Testing
Interview Questions:
1. Explain differences between Smoke Testing and sanity Testing?
Step 1: Business Requirements
Step 2: HLD
Step 3: Quotation
Step 4: FRS
Step 5: Build
Step 5: Deploy Testing server(SYS Server)
Step 6: Test Execution
6.1 Smoke Test execution
Step 7: Deveoper deployed Build 2 with defect fixes
What?
A type of testing which verifies whether the build is ready for
testing or not. Qualified enough to start testing or not.
Gmail:
1. Login
2. Registration
3. Change Pwd
4. Reset Pwd
5. Inbox
6. Sent Items
7. Drafts
8. Attachments
9. Settings
10. Logout
How to do smoke testing for Web Appication?
1. Build Deployment Success-->Server Logs
2. Landing page Load
3. Basic end to end flow
Smoke testing intenstion is to reveal critical
failures of the appication which are blocking the major
functionaity of the system
Ex: Load Failure
Missing of key fields/Features
Data connection broken(Data insertion to DB)
Server crash-Technical error page cannot be dispayed
Smoke Testing chracteristics are:
1. Smoke testing must be completed in short span of time
2. Smoke testing must be quick test which covers basic
end to end flow
3. No need to find all the defects ,the main purpose of smoke
testing is to find showstopper defects/Critical failures
When?
Scenario: You are the tester and you observed that smoke testing is
failed then what you will do?
Ans:
Step 1: Send all your results to Deveoper for confirmation
Step 2: Open the defect management tool and create the
Critical severity defect
Step 3: Update Environment down time tracker
Sanity Testing:
1. It is also not a detailed test
2. Sanity must be performed by testing before delivering the
appication to next level
Ex: Sanity regression
3. After depoying the tested application in UAT Server
If users/Client/Testers wants to do one more round of testing then Sanity testing is required to any any changes
4. If we are not having time to do comlpete testing then It is advisable to go for Sanity Test.
Smoke Testing vs Sanity Testing:
1. When compared to smoke test, sanity is more detailed and indepth test.
2. Smoke test must cover end to end flow of the appication, where as
Sanity need not be end flow flow
2.1 Important features
2.2 Frequently failed features
2.3 Critical to business
3. Smoke test must be preplanned with scripted test cases but sanity may not be end to end flow/end to end test cases(Adhoc testing)
4. Smoke testing will be done to know whether we can start testing
or not where as sanity test will be done before giving it
to next level
What?
How?
When?
Who?
What are the benefits of performing smoke testing?
What will happen if smoke testing fails?
Smoke Testing=BVT
-------------------------------------
1. Understand the changes made to the Build
2. Smoke Testing
3. Test the changes
4. Report the defects for changes made by deveoper
5. Retesting
6. Regression
----------------------------------------------------------------------- Sanity Testing:
-------------------------------------------------------
Comments
Post a Comment