Types of testing and test methodologies
1.Unit technologies:
It is also known as component test. It is done by the developer each and every small piece of code is tested.
2.Integration testing:
All these units are put together for testing. It is also done by the developer.
3.Smoke testing:
It is also known as dry test. Running the software to ensure that it is free from errors.
4.Black box testing:
It is used to check external functionality of the application. Here we will be giving the input and we will check whether the required output or not.
5.White box test:
It is also known as structured testing or glass box testing. We have to check for the internal process.
We have to check 1) conditions 2) loops 3) Database operations 4) memory leakages.
6.Grey Box testing:
It is a combination of blue box and white box testing.
7.Cosmetic testing:
It is for checking the appearance of the application. Here the appearance in the sense checking for the font style, size, color combinations, spellings and alignment.
8. Gorilla Test:
This is also known as monkey test. Running the software by performing illegal operations.
9.Stress test:
We have to run the application number of times to find whether the applications able to with stand the load or not. Here we are putting load in this test. In this we will test on an application.
10.Performance test:
We have to find out how much time is taking to perform a particular process.
11.Load test:
It depends on system configuration, operating system, data base. We have to find out how much load can a server take when multiple users access the same application present on the server at the same time.
12. Security test:
We have to check for the securities.
13.Recovery test:
There should be an option in the application for recovering the data from the back up.
14.Usability test:
This test is user-friendly. User-friendly means to find out whether the end user is comfortable while using the software. It is used for checking:
- Proper messages
- Keyword board operations are provided
- Navigation is proper
- Tool tip text
Bubble help or balloon help whether these applications are provided or not will check.
15.Compatibility test:
Running on various operating system that is window 98, 2000, Unix. Machines / browsers (internet explorer)
16.Retesting:
To find out whether the reported bugs have been fixed or not.
17. Regression test:
We have to ensure that the modifications are giving rise to any other side effects. We will check inside the application.
18.Sanity test:
We have to see that operating system, database connectivity and network connections are not getting disturbed.
19.System testing:
The entire application is tested for the functionality, performance, security, recovery, compatibility and usability.
20.Installation test:
Load the application in some other system and find whether it is getting load properly or not.
21. Uninstallation test:
Unload the software and check whether all the components are getting removed or not.
22. Alpha test:
We will be running the software from the developers place and giving demo to the clients from the developers place and then getting a feedback from the clients.
23.Beta test:
We will be giving the software to the clients place and asking the check to them and then they use the software and then we will get some feedback. I this testing the developers put some licenses after that time period it will expire.
24.User application test:
End user is used to test the software to find out whether all the requirements have been full filled or not.
End user will check for:
Software testing
Documentation
Training