SMOKE
TESTING:-
è Smoke Testing
is performed to ascertain that the critical functionalities of the program is
working fine.
è The objective
of this testing is to verify the "stability" of the system in order
to proceed with more rigorous testing
è This testing is
performed by the developers or testers
è Smoke testing
is usually documented or scripted
è Smoke testing
is a subset of Acceptance testing
è Smoke testing
exercises the entire system from end to end
SANITY TESTING:-
è Sanity Testing
is done to check the new functionality/bugs have been fixed
è The objective
of the testing is to verify the "rationality" of the system in order
to proceed with more rigorous testing
è Sanity testing
is usually performed by testers
è Sanity
testing is usually not documented and is unscripted
è Sanity testing
is a subset of Regression Testing.
è Sanity
testing exercises only the particular component of the entire system.
Importance of
Sanity Testing
è Sanity testing makes the tester confident about the
functionality of an application.
è Sanity testing assures that the part of the system
or methodology works roughly as expected.
è Using sanity testing the testers makes sure that the
basic functionality of an application is working fine and the proposed
functionality works roughly as expected.
è By performing sanity testing on a mobile
device testing will be sure that the application will be working fine on other
mobile devices that have the same operating system.
è Sanity testing is not documented and thus it saves
time and is easy to perform.
è Sanity testing gives a rough idea of the
functionality of the application and the number of uncertainties in the
application due to bug fixes.
è Sanity testing is beneficial when the time for a
particular project is limited and the tester has already checked the project in
detail.
è Sanity testing does not require many testers and
thus saving testing efforts.
è Gives a quick state of the product to the developers
after they have done changes in the code.
No comments:
Post a Comment