In software industry different levels of testing performed before project is going to launch; in this blog I am going to discuss these levels of testing. Here I like to discuss under different methodologies. The two levels of Software Testing given below; in this blog I am going to discuss level of Functional Testing.
Functional Testing is based on the specifications of the software that is to be tested just like black box testing. First of all the application is tested by providing input and then the results are examined what it intended for. This testing is done on a complete, integrated system. Following are the number of steps in Functional testing given below.
Find out the functionality that the intended application is meant to perform.
It is based on the specifications of the application.
The testing output based on the test data and the specifications of the application.
4. Find out the entire test Scenarios and the execution of test cases.
5. The results based on executed test cases while comparing the actual and expected results.
Unit testing is performed by the developers before the application is handed over the testing team. The developers test individual units of source code assigned areas and make sure that the objective of this testing is to isolate each part of the program and show that individual parts are correct in terms of requirements and functionality.
Limitations of Unit Testing
Unit Testing cannot resolve each and every bug in an application. It becomes difficult to evaluate every execution path in every software application. The test scenarios and test data which are used by developer are limited.
Combining all the parts of an application to find out whether it functions correctly together or not. We can use two methods of Integration Testing i.e. Bottom-up Integration testing and Top Down Integration testing.
The testing of combined parts of an application to determine if they function correctly together is Integration testing. There are two methods of doing Integration Testing Bottom-up Integration testing and Top Down Integration testing.
Top-Down integration: Highest-level modules are tested first and lower level modules are tested after highest-level get completed.
Bottom-up integration: This testing starts with unit testing, followed by tests of gradually more high-level combinations of units or modules.
In system testing the application is tests as a whole after all the components are integrated and this testing performed by specialized senior testing team to check whether quality is maintain or not.:
System testing play important role because of following reasons:
1. In Software Development Life Cycle (SDLC).
2. The application is tested carefully to verify all the functional and technical specifications.
Regression testing is done to avoid the fixed bug has not resulted in another functionality or business violation. The main intention of Regression testing is to ensure that a change, such as a bug fix did not result in another application.
A special testing team measure whether the application meets the intended specifications and able to satisfy the clients’ requirements. The testing team has pre written scenarios and Test Cases that will be used to test the application.
The combination of system testing, integration testing and unit testing are called alpha testing. The following will be tasted in the application i.e. spelling Mistakes, Broken Links, and Cloudy Directions.
Beta testing is done after Alpha testing has been successfully performed. Intended audience tests the application and so it also known as pre-release testing. Users will run the application and send his/her feedback to the project team