Friday, 26 July 2013

TYPES OF TESTING

TYPES OF TESTING

1.       Build Verification Testing.
2.       Regression Testing.
3.       Re – Testing.
4.       Alpha - Testing.
5.       Beta - Testing.
6.       Static Testing.
7.       Dynamic Testing.
8.       Installation Testing.
9.       Compatibility Testing.
10.    Monkey Testing
11.    Exploratory Testing.
12.    Usability Testing.
13.    End – To – End Testing.
14.    Port – Testing.
15.    Reliability Testing
16.    Mutation Testing.
17.    Security Testing.
18.    Adhoc Testing.
19.   Scalability Testing.
20.   Heuristic Testing.
21.   Accessibility Testing.
22.   Performance Testing
23.   Load testing
24.   Stress Testing
25.   Volume Testing
26.   Context Driven Testing
27.   Comparison Testing
28.   Globalization Testing

1. Sanitary Testing / Build Verification Testing / Build Accepting Testing.

It is a type of testing in which one will conduct overall testing on the released build in order to check whether it is proper for further details testing or not.
Some companies even call it as Sanitary Testing and also Smoke Testing. But some companies will say that just before the release of the built the developer’s will conduct the overall testing in order to check whether the build is proper for detailed testing or not that is known as Smoke Testing and once the build is released once again the testers will conduct the overall testing in order to check whether the build is proper for further detailed testing or not. That is known as Sanitary Testing

2. Regression Testing

It is a type of testing in which one will perform testing on the already tested functionality again and again this is usually done in scenarios (Situations).
  Scenario 1:
Whenever the defects are raised by the Test Engineer rectified by the developer and the next build is released to the testing department then the Test Engineer will test the defect functionality and it’s related functionalities once again.
  Scenario 2:
Whenever some new changes are requested by the customer, those new features are incorporated by the developers, next built is released to the testing department then the test engineers will test the related functionalities of the new features once again which are already tested. That is also known as regression testing.
  Note:
Testing the new features for the first time is new testing but not the regression testing.

3.  Re – Testing:

It is a type of testing in which one will perform testing on the same function again and again with multiple sets of data in order to come to a conclusion whether the functionality is working fine or not.

4.  Alpha - Testing:

It is a type of testing in which one (I.e., out Test Engineer) will perform user acceptance testing in our company in the presents of the customer.

Advantages:

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

5. Beta - Testing:

It is a type of testing in which either third party testers or end users will perform user acceptance testing in the client place before actual implementation.

6. Static Testing:

It is a type of testing in which one will perform testing on an application or it’s related factors without performing any actions.
Ex:     GUI Testing, Document Testing, Code reviewing and etc…

7.  Dynamic Testing:

It is a type of testing in which one will perform testing on the application by performing same action.
Ex:     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 guidelines given in the deployment document and if the installation is successful the one will come to a conclusion that the guidelines are correct otherwise the guidelines are not correct.

9. Compatibility Testing:

It is a type of testing in which one may have to install the application into multiple number of environments prepared with different combinations of environmental components in order to check whether the application is suitable with these environments or not. This is use usually done to the products.

10. Monkey Testing:

It is a type of testing in which one will perform some abnormal actions intentionally (wanted) on the application in order to check its stability.

11. Exploratory Testing:

It is a type of testing in which usually the domain expert will perform testing on the application parallel by exploring the functionality without having the knowledge of requirements.

12.  Usability Testing:

It is a type of testing in which one will concentrate on the user friendliness of the application.

13. End – To – End Testing:

It is a type of testing in which one will perform testing on a complete transaction from one end to another end.

14. Port Testing:

It is a type of testing in which one will check whether the application is comfortable or not after deploying it into the original client’s environment.

15. Reliability Testing (or) Soak Testing:

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

16. Mutation Testing:

                It is a type of testing in which one will perform testing by doing some changes
For example usually the developers will be doing any many changes to the program and check its performance it is known as mutation testing.

17. Security Testing:

                It is a type of testing in which one will usually concentrate on the following areas.
i)  Authentication.
ii) Direct URL Testing.
iii) Firewall Leakage Testing.
 i) Authentication Testing:
it is a type of testing in which a Test Engineer will enter different combinations of user names and passwords in order to check whether only the authorized persons are accessing the application or not.
 ii) Direct URL Testing:
It is a type of testing in which a test engineer will specified the direct URL’s of secured pages and check whether they are been accessing or not.
 iii) 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 unauthorized pages in order to check whether the firewall is working properly or not.

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.

19 .Scalability Testing

It is a type of testing in which one can perform testing on the application to check if the application is enhance able / expandable and measurable without having to do with design changes and environmental alterations.

20. Heuristic Testing

It is a type of testing in which the test engineer performs testing on the application based on the past experience to ensure through testing and complete coverage in the testing.

21. Accessibility Testing

       It is a type of testing in which the test engineer checks the application if it has accessibility factor. In other words he checks if the application is able to serve the abnormal disable users apart from normal users.

22. Performance Testing

performance testing is testing that is performed, from one perspective, to determine how fast some aspect of a system performs under a particular workload. It can also serve to validate and verify other quality attributes of the system, such as scalability, reliability and resource usage.

23. Load Testing

Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system's response time degrades or fails.

24. Stress testing

Testing the stability and response time of an application by applying the load which is more than design load

25. Volume Testing

Testing the stability and response time of an application by passing the huge volume of data across the application

26. Context-driven testing

          Testing driven by an understanding of the environment, culture, and intended use of software. For example, the testing approach for life-critical medical equipment software would be completely different than that for a low-cost computer game.

27. comparison testing

          comparing software weaknesses and strengths to competing products.

28. Globalization testing

                        Developing the application in multiple languages is known as globalization. Testing this kind of application is called as globalization testing. We need to test the application for different languages example: - English, French, Chinese etc.
It is of two types:-
1.    Localization testing.
2.    Internationalization testing.
internalization testing
                     It is the testing done to check the application is working on different platforms of international languages.
Ex: - Spanish, German etc.

localization testing
                   It is the testing done to check the application is working on different platforms of local languages.

 Ex: - Win 95/98/2000 etc.

part time/full time home available at http://www.dataentryjobs.us/143316.html

No comments:

Post a Comment