What is the difference between smoke testing and sanity testing?
Answers were Sorted based on User's Feedback
Smoke Testing is the first thing we do on AUT. Anytime the new build is deployed, smoke testing is the first step. In this we check that whether or not our aplication is running properly or not. and also we check that correct version is installed .
and Sanity testing is the functional testing and to check the most critical functionality is working or not.
First Smoke is performed and then Sanity.
Is This Answer Correct ? | 4 Yes | 0 No |
Answer / deepthy
Smoke Testing is performed to ascertain that the critical functionalities of the program is working fine
This testing is performed by the developers or testers
Smoke testing is usually documented or scripted
Sanity Testing is done to check the new functionality / bugs have been fixed
Sanity testing is usually performed by testers
Sanity testing is usually not documented and is unscripted
Is This Answer Correct ? | 2 Yes | 0 No |
Answer / sunita
smoke testing is initial phase testing of sanity testing.
sanity testing is testing of measure functionality testing of app.
Is This Answer Correct ? | 1 Yes | 4 No |
Answer / kiran wale
Sanity and smoke testing are the last phase when all the integration of the modules are done.After this you have to select between these two testing.
Always have to understand that smoke testing is cursory testing of the whole software or we can say basic functionality of the software while sanity testing is in depth testing of any one module selected from the software.
Both sanity and smoke testing are implements when time is limited and software have to be launch.
Is This Answer Correct ? | 1 Yes | 5 No |
Hi, Can anyone suggest a test case writing technique for the below scenario. 1. User draws a lines on the image 2. User selects the lines and right clicks ( Measuremnts like distance between the start and the end point, coordinates of start point and coordinates of end point) 3. User selects one of the measurement Measurement is displayed Just want to highlight, i am looking for a test case writing technique for above scenario.
Whenever developer will recieved the defect from the tester,then he will go thru the defect whether it is acceptable or not?for that he will execute that application again,while executing if he did not found any such type of defect(what we are rise the defect above),then he will send that defect to the corresponding tester with status of 'reject',as a tester what we can do?(here writing the reproduce steps and attached screen shots has been done by tester while sending the defect to the developer, no need to send reproduced steps and screen shots again)
Guys, can any one of u give the realtime example for Regression Testing
difference Between Quality assurance and Quality control
write test case for login window
Hierarchy of Regression Testing?
What is the difference between unit testing and smoke testing
what is Testing environment in your company ,means hwo testing process start
what is regression testing?
How we validate and creating frameworks?
Main concepts in webpage Testing?
i have an iphone 4g can you tell me the test case for the camera?