difference between sanity testing and smoke testing?
Answer Posted / subhash ingale
1. Sanity Testing or Build Verification testing or Build
acceptance testing.
It is type of testing in which one will conducted overall
testing and the release the build in order to conform
whether the build is proper or not for conducting detil
testing.
To do the same one will check the following.
1.Whether the build can installed in to Environment proper
or not.
2.whether one can navigate to all the pages of the
application or not.
3.whether all the objects are available and properly
arranged or not.
4.whether the required connection are properly established
or not.
Smoke Testing :-
some compines this type of testing also called as smoke
testing but in some compines just before releasing the
build is proper or not that is known as smoke testing and
once the build is release the test Eng. will check whether
the build is proper or not . that is known as build
acceptance testing ,build verification testing.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
Explain test metric and the information it provides.
About Hierarchy level in your company.
What is data matrix? What is the use of it?
.In languages testing, what is the fixed part and changing part?
few automation basic questions One question to write a scriot in any language you know.
What is meant my Firewall testing? how the testing is performed on it?
how can we do database testing. In database testing we verify the data integrity and data validation. how can we do testing of Index, triggers, views, ransactions,cursors etc
is it not possible to automate full project??what r the parts in project that cant be automated(tht has to be done manually)?
how will you estimate of your website?
Can any one say me how to do Performance testing step by step plz for a desktop application(offline application).all the data is stored in internal server itself can any plz help me. ts quite urgent friends.
Why we have to do manual testing?
Can you explain v model in manual testing?
How do test documents in a project span across the software development lifecycle?
Can you explain steps in function points?
Define performance and stress testing?