Build accepter testing (or) Build verification (or) Sanitary Testing:
It is a type of testing in which one will conduct over all testing on the released build in order to conform whether it is proper for conducting detailed testing(or) not.
To do the same one will check the following:
I. Whether the build can be properly installment into the environment or not
II. Whether one can navigate to all the pages and applications or not
III. Whether all the important objects available or not
IV. Whether the required connections are properly established or not
In some company’s they will call this type of testing is smoke testing also. But in some company’s soon after the build is developed just before releasing the build developers will check whether the build proper or not that is known as smoke testing and once the build is released the test engineer will once again will check the same that is known as build accept testing & sanitary testing.
Regression testing: It is a type of testing in which one will perform testing on the already tested functionality again and again usually you do it 2 scenarios. Ex: car lighting testing
Ø Whenever the defects are raised by the test engineer, after rectification the next build is released them the test engineer will check defect functionality as well as the related functionality once again.
Ø Whenever some new features are added to the application, next build is released then the test engineers will check all the related functionality of those new features once again in order to conform whether they are working fine or not.
Note: testing the new feature for the first time is new testing but not regression testing.
Re-testing: It is a type of testing in which one will perform testing on the same functionality again and again with multiple sets of data in order to come to a conclusion whether it working fine or not.
Note: re testing starts from the first build to last build
Ø Regression testing starts from second build and continue up to last build
Ø During regression also retesting will be done usually people call this as re and regression testing.
Å“ testing: It is a type of user acceptances testing conducted in the software company by their test engineers in the presence of the user just before delivery.
β testing: It is a type of testing in which one (either end users or third party testing experts) will perform testing in the customers place just before actual implementation.
Ex: look&feel static, GUI
Static testing: It is types of testing in which one will perform testing on the application are its related factors without performing any actions.
Ex: GUI testing, document testing, code review etc.
Dynamic Testing: It is a type of testing in which one will perform the application or its related factors by performing some actions.
Ex: functionality test. (Bus journey secendrabad or charminar guidelines)
Installation testing: It is a type of testing in which one will install the application into the environment by following the guide lines provided in the deployment document in order conform whether those guide lines are suitable for installing the application in to the environment or not.
Ex: installation process
Comparability testing :( suitable) it is a type of testing in which one will install the application into the multiple environments prepare with different combination in order to conform whether the application is suitable to those environments or not.
Usually this type of testing is important for product rather than project.
Monkey testing: It is a type of testing in which one will perform abnormal action intentionally on the application in order to check the stability (standby) of application.
Exploratory testing: It is a type of testing in which one will (domain expert) test the application without having the knowledge the application just by exploring the application.
Exploring: having the basic knowledge of some concept doing something and knowing more about it is knowing as exploring.
Usability testing: It is a type of testing in which one will check the user friendliness of the application.
Ex; application open cursor wait starting point or not.
End to end testing: It is a type of testing in which one will perform testing on the end to end scenarios or the application.
Port testing: It is a type of testing in which one will install the application into the original customer environment and check it is suitable environment or not.
Soaking testing/ reliability testing: It is a type of testing in which one will perform testing one the application continues for long period of time in order to check the stability of the application.
Security testing: It is a type of testing in which one will check whether application is properly protected or not. To do the same block box test engineers will implement following types of testing.
Authentication testing: It is a type of testing in which one will enter different combinations of user names and passwords and check whether only the authorized people are accessing people or not.
Direct URL testing: It is a type of testing in which one will enter the direct some URL secure pages and check whether they are able to access them are not.
Fire wall in case testing/ User prevails testing: It is a type of testing in which one will enter into the application as a one level of user and will try to access the application beyond its limits and check weather is able to access or not.
Mutation Testing: It is types of testing in which one will perform testing on application are its related factor by during some changes to them.
Ad-hoc testing: It is a type of testing in which one will (test engineer) perform testing on the application in their own style after understanding the requirements clearly. Usually this type of testing is after formal testing.
Ex: temporary random
