Different Types of testing are used to test software functionality during Software Development Life Cycle
Software testing is used to assess the quality of the software and check a routine in the sense of making sure that it is right.
Types of testing are as
1. Manual Testing -:
Manual testing is a process executing test cases without using automation testing tool. It identify unexpected behavior or bug, ensure that application is error free and conformance user specified requirement testing by manually.
It covers 100% test coverage
2. Unit Testing -:
Unit testing is a process of testing individual unit of source code assigned to do. It is tested by manually or respective developer. It requires detailed knowledge of internal program code. It is also called as component and module test
3. Integration Testing -:
Integration testing is a systematic techniques of identifying errors that can occurs when individual components or modules or chunk of source code are combined together. It check whether data is lost or not across an interface. Also checks the communication or behavior of system after combined different modules.
It is tested by developer as well as tester. Integration testing follows number of incremental testing strategies while constructing the programs which are
– Top-down Integration
– Bottom-up Integration
– Big bang
4. System Testing -:
System testing is a process of testing sequence of work that has been properly integrated or not. It tests whether system performs allocated functions. Primary purpose of system testing is fully exercise the computer based system according to user specifies requirement. It follows black box testing. It divides into two parts like functional testing and non functional testing
It is tested by tester only.
5. Regression Testing -:
Regression testing is a process of re-execution of few functionality of test that has already been carried to ensure that changes have not been propagated unintended side effects. It tests new modified functionality with old to ensure that faults have not been introduced in old functionality. It helps to discover error re-correct error and check behavior of the system after modification or in updated version
6. Recovery Testing -:
Recovery testing has ability to restart operations after the integrity of the software application has been lost.
It is used to recover (must be corrected) from faults and resume processing within prescribed time period.
7. Acceptance Testing -:
Acceptance testing is a testing technique which is used to determine whether system met user specified requirements or not. It assesses the system’s readiness for deployment and users use. It focuses mainly on validation testing whereby trying to determine whether the system is fit for user specified functionality.
Acceptance testing should answer questions like ‘ Is it system ready to release?’ ‘Has development met their requirement’.
Types of accepting testing are as
– User acceptance testing
– Operational acceptance testing
– Alpha testing
– Beta testing
8. Stress Testing -:
Stress testing is the process of determining the ability of testing beyond the limits of normal operations. It determine the robustness under heavy load than on what would be considered and check behavior of system. It is type of non functional testing. It is also called torture testing. Stress testing used for
– To determine stability of system
– To determine breaking point or limit
– To check performance under heavy load
9. Load Testing -:
Load testing is a sequences of activity which test the system performance steadily and constantly increasing the load on system till the time it reaches high or peak load. It perform to determine system behavior under normal and peak load conditions. It is used to identify the maximum operating capacity. Load testing measure the performance of software application by simulating multiple users accessing the program concurrently.
It is type of non functional testing.
Goal of load testing is
– To measure website performance
– Determine elements causing for degradation
– Measure response