Interested to Buy Any Domain ? << Click Here >> for more details...
difference between smoke and sanity testing?
help me with the clear answer...
- 5 Answers
- 10052 Views
- Cap Gemini, Polaris, I also Faced
- E-Mail Answers
Answer Posted / shilpa
Smoke Testing: To check whether the build is proper or not before releasing the build is called Smoke Testing.
Sanity Testing: After releasing the build Test Engg will check whether the build is proper or not is called Sanity Testing.
Usually We check the following:
1. Whether the build can be properly installed into the environment or not .
2.Whether one can navigate to all the areas of the application or not.
3.Whether all the important features are available or not.
| Is This Answer Correct ? | 13 Yes | 3 No |
Post New Answer View All Answers
How will you do beta testing?
Write positive and negative test cases for forgot password?
How to write test case for view the table(i.e it is already stored in database and see the content in the table)
what are metrics and what are metrics did u collect in you are project
Which model is following in your company for developing software?
Tell me agile process in your company
Anyone tell me the test cases of Shopping Favorite
What do you do (with the project tasks) when the schedule fails?
Hi there, I am new to the world of testing. Is there any place where I can have a look at an actual specification documents or test plans or test cases. This will help me in generating a level of confidence. Looking forward to your replies
what technical problem u face in your module please tell what is it mean its any bug or anything else i want ans give any example which ever modul u r working for u can give me any example
What are differences between Testing in Uncontrolled Environment and Abnormal Environment?
Can any1 tell me suppose u r doing manual testing on unix platform with Shell Script, then how it is done? How u r implementing it & what is the use of Shell scripting on Manual Testing?
A form has four mandatory fields to be entered before you submit. How many numbers of test cases are required to verify this? And what are they?
If there is non reproducible bug which developer is not ready to agree, how you will convince him.
What is decision table testing?
