SOFTWARE TESTING TYPES

TYPES OF TESTING

 

 

1. Build Acceptance Testing Or Build Verification Testing Or   Sanity  Testing: -

          It is a types of testing in which one will conduct over all testing on the released build in order to check whether it is proper for further detailed testing or not. Even some companies call it as smoke testing, but some companies says that just before releasing the build the developers will conduct the overall testing on the build that is known as smoke testing and once the build is released whatever the test engineers do in order to accept the build is known as B.A.T or B.V.T or Sanity Testing.

2.Regression Testing: -

          It is a type of testing in which one will perform testing on the already tested functionalities again and again.

It is usually done in two scenarios.

1.    Whenever the testers has raised the defects, rectified by the developers and next build is released to the testing department then the test engineer’s will test the defect functionality as well as the related functionality once again.

2.    Whenever some new features are incorporated by the developers, next build is released to the testing department then the test engineers will once again test the related functionalities of the new features in order to confirm that they are working same as previous.

Note: - Testing the new functionalities for the first time is known as new testing but not Regression Testing.

3.Re-Testing: -

          It is a type of testing in which one will test the same functionality again and again with different sets of values in order to come to a conclusion whether it is working or not.

4.a- Testing (Alpha Testing): -

          It is a type of user acceptance testing in which the test engineers will test the application in our company, in the presence of the customer.

Advantage: - If at all any defects are found then there is a chance of rectifying them immediately.

5. b-Testing (Beta): -

It is a type of user acceptance testing done in the clients place either by the end-users  or by the third party testing experts before actual implementation.

Drawback: If at all any defects are found then there is no chance of rectifying them immediately.

6. Static Testing: -

          It is a type of testing in which one will perform testing on the application or application related factors without performing any action.

Eg:- Documentary testing, GUI testing, Code reviews and etc.,

7. Dynamic Testing: -

          It is a type of testing in which one will perform in the application or its related factors by doing some actions

Eg: - Functional testing.

8.Installation Testing: -

          It is a type of testing in which one will install the application in to the environment by following the guide lines provided in the installation document and if the installation is successful then he will come a conclusion that the given guide lines are correct otherwise he will come to a conclusion that the given guidelines are not correct.

9.Compatibility Testing: -

         

          It is a type of testing in which one may have to deploy the application in to the multiple number of environments prepared with different combinations of environmental components in order to check whether the application is compatible with all that environments. This type of testing is usually done to products.

10. Monkey Testing: -

          It is a type of testing in which one will perform abnormal action on the application intentionally in order to check the stability of the application.

11.Usability Testing: -

          It is a type of testing in which one will check whether the application is user friendly or not and it can be comfortably used by the end user or not.

12. Exploratory Testing: -

          It is a type of testing in which one (Domain Experts) will will perform testing on the application with out having the knowledge of requirements but by exploring the functionality.

13.End-To- End Testing: -

          It is a type of testing in which one will perform testing on all the end- to-end scenarios of the application.

14.Port Testing:-

          It is a type of testing in which one will deploy the application in to the clients environment and check whether it is compatible with that environment or not.

15.Reliability Testing: -

          It is a type of testing I which one will perform testing on the application continuously for long period of time in order to check the stability of the application

16.Security Testing: -

          Its is a type of testing in which one will concentrate on the following areas of the application

          a.   Authentication Testing

          b. Direct URL Testing (Uniform Resource Location)

          c. Fire Wall Leakage Testing.

(a) Authentication Testing: -

          It is a type of testing in which one will enter different combinations of usernames and passwords and try to access the home page in order to check whether only the authorized persons are accessing the application or not.

(b) Direct URL Testing: -

          It is a type of testing in which one will enter the URL of an unauthorized page directly in the browser and try to access that page in order to check whether it is been accessed or not.

(c) Firewall Leakage Testing: -

          It is a type of testing in which one will enter as one level of user and try to access the other level of unauthorized pages in order to check whether the firewalls are working properly or not.

17. Mutation Testing: -

          It is a type of testing in which one will perform testing on something by doing some changes to it.

18. ADHOC Testing: -

          It is a type of testing in which one will perform testing on the application in his own style after understanding the requirements clearly.