10. Testing Types
10. Testing Types
Software Testing means checking or testing the particular software application or program
according to the perspective of end user’s requirement.
Under functional testing we provide specific predefined input and check what output
system is generating.
1. Smoke
Example:-www.amezon.com,
We just need to check whether the given link/module /software is working or not.
Means by entering above link into browser the should working i.e. it should open.
2. Sanity
Under Sanity testing we go for the in-detailed testing of the application. Covered most of the
Functionality.
3. Unit
In unit testing we are going to check the main module into different parts i.e. Unit. When we
get build into our Environment (QA) we generally performed the Unit Testing first.
4. Integration
Once we get multiple modules for testing we performed integration testing. In which check the
communication between two or more Dependable module. Here we check data transferred
from one module into another.
5. System Testing
End to End testing is called as System Testing. Here whole application is tested.
To perform the UAT testing first QA Testing is done. Then this piece of software is pushed
into UAT Environment. In UAT whole system is tested thoroughly before deployment of that
piece of software.
A. Alpha Testing :-
B. Beta Testing :-
A. Alpha Testing :-
Generally alpha testing is performed in our side/UAT as per client environment. Post
Alpha Testing the software is ready for deployment into client Environment.
B. Beta Testing :-
Beta Testing Done into client side, where whole system is tested as per the client
Environment. Generally Beta and Alpha testing are done by two separate team.
Largely it is done by Team who is functional user of that software. As a QA Team we assist
them as per request from the client.
7. Retesting
Retesting is done after fixing the defect. To validate that present defect is actually fixed or
not.
8. Regression
Regression testing is done to check whether the existing functionality get affected by the
changes happen into the Software. In short what are the impact has happened on dependent
module is checked here.
In Non Functional type of Testing we check how system is giving the output. Here
we check the Performance of software under different conditions.
1. Load
2. Stress
3. Endurance
4. Volume
5. Security
6. Installation
7. Accessibility
8. Configuration
9. Globalization
10. Localization
11. Scalability
1. Load
2. Stress
We test the system until it get breaks. When extreme stress is applied to the
system, then need to test the maximum limit of the system to support until is breaks.
3. Endurance
Here we check that, what is the maximum load that system can support for
specific time period. To test this we slowly increase the volume and check the
performance of the system.
4. Volume
In Volume Testing we apply huge data to system until it get hang. Generally
this test is performed to check how system is responding to bulk of user at a time.
Ex:- On result date when many government web site get hang because of huge load is
applied to system.
5. Security
Under security testing we check the how the data is protected from the un
authorized user.
6. Installation
We test here that the particular software is properly installed or not. Need to
test that whether particular software will be working post installation. Look for proper
hardware, software properly installed as per documentation.
7. Accessibility
8. Configuration
9. Globalization
Under this Testing we need to test the application from the divers (diversity)
user perspective. Application such as Facebook, YouTube, Google, Gmail etc has to be
checked with consideration of global parameters like Different languages, time zone,
ethnicity, etc.
10. Localization
11. Scalability
We need to test for how much people it is accessible at a time. On what scale of
divers ,volume of people will able to use the particular application that we have to test.