Testing Types
-Kiran Kumar
Sanity
Testing :
When there are some minor issues with software and a
new build is obtained after fixing the issues then instead of doing complete
regression testing a sanity is performed on that build. You can say that sanity
testing is a subset of regression testing.
Sanity testing is done after thorough regression testing is over, it is done to make sure that any defect fixes or changes after regression testing does not break the core functionality of the product.It is done towards the end of the product release phase
Sanity testing is done after thorough regression testing is over, it is done to make sure that any defect fixes or changes after regression testing does not break the core functionality of the product.It is done towards the end of the product release phase
.
Sanity testing follows narrow and deep approach with detailed testing of some limited features.
Sanity testing follows narrow and deep approach with detailed testing of some limited features.
Sanity
testing is like doing some specialized testing which is used to find problems
in particular functionality.
Sanity testing
is done with an intent to verify that end user requirements are met on not.
Sanity
tests are mostly non scripted.
Smoke
Testing:
Smoke Testing, also known
as “Build Verification Testing”, is a type of software testing that comprises
of a non-exhaustive set of tests that aim at ensuring that the most important
functions work. The results of this testing is used to decide if a build is
stable enough to proceed with further testing.
The term ‘smoke testing’, it is said, came to software
testing from a similar type of hardware testing, in which the device passed the
test if it did not catch fire (or smoked) the first time it was turned on
Difference between Smoke and
sanity Testing?
SMOKE Testing- When
testing team receives the build from the Development team first time, testing
team executes the selected test cases which covers the major functionality of
the application. if all the major functionality is working fine than testing
team accept the builds for further testing.
Smoke testing is scripted.
Sanity Testing- When testing receives the build
with minor changes, testing team checks the particular functionality. its
working or not. it has not the selected test cases.
Sanity testing is unscripted.
Static
Testing:
One perform testing on the application or application related factors
whenever it is not being executed.
Ex:
Document Testing, GUI Testing.
Alpha Testing:
It is a type of Acceptance Testing.Test engineer perform
testing on an application in the presence of User/customer within the
company(Developers site).
Beta Testing:
This type of Acceptance Testing
conducted at clients place either by third party ttesting units or by the end
users.
Dynamic
Testing:
One
perform testing on an application when ever it is being executed.
Ex:
Functionality Testing.
Compatablity
Testing:
A test engineer may have to deploy
application into the environments prepared with different environmental
conditions like Browser, Application Server,
Web servers, Operating Systems, databases and check whether the
application is compatable with those environments.
Soak Testing:
It is also a type of STRESS
testing.Test engineer will perfom testing on the application for longer period
of time and check whether the application is stable or not.
Usability
Testing:
It is a type of testing in which
test engineer will only focus on the user friendliness of the application.
0 comments:
Post a Comment