What is the difference between smoke and sanity testing?
and when we perform smoke testing and when we perform
sanity testing?
Answers were Sorted based on User's Feedback
Answer / rajeshwar rao
Smoke testing is useful for checking for the main
funcnality of the application.it is also initial type of
testing. in these chech the futures of the application>
sanity testing also initial type of testing it is also
called as tester accptance testing.to check the build is
stable or not.
smoke tetsing and sanity testing conceptually they are same
but perceputally they are different.
smoke testing is negitive point of view.sanity testing is
positive point of view.
Is This Answer Correct ? | 4 Yes | 0 No |
Answer / abhishek kumar
Sanity testing:- After receiving initial build from
development team,test engineers estimate stability of that
build before start testing.This type of observation is also
known as "Testability testing"or"tester acceptance testing"or
"build verification testing".
Smoke Testing:-It is small shakeup in sanity testing.During
smoke testing,test engineer rejects build with appropriate
reason,when that build doesn't work properly.
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / chaitanya
HI Friends,
Smoke testing is the kind of testing that
is done by the white box testers ,generally this is done by
the developers before giving the developed application to
the black box testers.
Sanity testing is the kind of testing
done whether to check the application developed by the
developers is proper for detailed testing. This is done by
the black box testers. Here "PROPER" has four conditions,
1. Whether the application is installed properly in the
test environment or not,
2. Whether one is able to navigate all the pages or links
of the applications
3. Whether all the functionalities are available.
4. Whether connections with the database are established.
Lastly,, Sane in english means "Proper" SO checking the
application before the detailed testing is what is Sanity
Testing.
Hope you guys are clear on this.
.........Chaitanya.
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / vru.babu
hello sara,
u reverse the total definition of smoke testing and
sanity testing ok.
Smoke testing - A process of testing weather the CODE is
ready to submint for testing or not
this is Developer part after coded developer will do
Sanity testing - A process of testing weather the BUILT is
ready for further testing or not
in this we people check for stebility of the build
this is tester part.
Is This Answer Correct ? | 0 Yes | 1 No |
Answer / sara
Smoke testing - A process of testing weather the BUILT is
ready for further testing or not
this is tester part.
Sanity testing - A process of testing weather the CODE is
ready for further testing or not
this is Developer part after coded developer will do
Is This Answer Correct ? | 1 Yes | 3 No |
Answer / raj_rex
SMOKE TEST :
Smoke testing is considerd as
built level test.Each time the test team receives a new
build(new version of program),an initial test is performed
to determine that the most crucial functions of the program
works and the build is stable enough and can be considered
for further testing.
SANITY TEST :
Sanity testing is considered as
release level testing.When software is ready to be shiped
to client and we want to finally cheek if everything is
fine and working as per requirement.It's a sub set of
Regressing testing -a group of test cases are executed to
cheek it is indeed working according to specification
(requirement).
I hope this will do.But somebody may not agry with me as
this defination will vary company to company... but i think
this is the basic defination...
Is This Answer Correct ? | 0 Yes | 4 No |
Can any one please tell me the exact difference between the smoke testing,sanity testing and exploratory testing?
Why should you care about objects and object-oriented testing?
The Managment is saying Stop Testing immediately some reasons.... What will you do at that time....
How you manage your test case (already written )when requirments changes?
what is adhoc testing n when it wil be done?
if we are working on web app and suddenly web app server crush or block ..that situation wht will we do.. and which command will use in sql database
After project was released to customer the customer find a defect in u r build. the build is related to that area which u had tested that. so u r TL comes and asks u then how will u convince u r TL and The customer
can any body explain about BVA and ECP briefly?
When the Developer fixes and releases a defect.. then the tester tests it and fails the defect. Suppose the developer again fixes it and the tester again fails it and this process continues for the same defect for more times then what is that u do for getting the defect closed?
Hello people...im planning to jump into Manual Testing field. How should i start. Please guide me.. Thank you
What is Test Strategy and Test Plan..what is the Diff.between those?
while reading specification documents if u got any doubts or u think the specification should be clear or when u think some changes should be there in specifcation docs, or u find the difference in FRS and Design docs,whom do u report this??