welcome to XRM blog

Keep in touch with latest CRM/ERP articles

To remain competitive your organisation must be efficient across the business process spectrum. To do so you need to take sound decisions based on a balance between the cost and risk. To do so you will be heavily dependent on your content management in itself needs...


Levels of Functional Testing

By Rajesh on 4/29/2014

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
  • Non- Functional Testing

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

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.

Integration Testing

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.

System Testing

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

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.

Acceptance Testing

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.

Alpha Testing

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

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

Testing Tools
Functional Testing
Levels of Testing
Blog Calendar
Blog Calendar List
2019 Jan  9  3
2018 Dec  10  4
2018 Nov  52  3
2018 Oct  12  3
2018 Sep  27  11
2018 Aug  2  2
2018 Jun  11  1
2018 Jan  44  2
2017 Sep  369  5
2017 Aug  15  1
2017 Jul  15  2
2017 Jun  37  2
2017 May  17  1
2017 Apr  31  2
2017 Mar  105  4
2017 Feb  274  4
2016 Dec  173  3
2016 Nov  275  8
2016 Oct  199  10
2016 Sep  346  6
2016 Aug  38  1
2016 Jun  1602  6
2016 May  102  3
2016 Jan  68  2
2015 Dec  377  6
2015 Nov  3  1
2015 Oct  12  1
2015 Sep  1130  6
2015 Aug  11  1
2015 Jul  102  2
2015 Jun  7  1
2015 May  20  1
2015 Apr  21  2
2015 Mar  67  3
2015 Jan  5024  4
2014 Dec  14  1
2014 Nov  2167  4
2014 Oct  74  2
2014 Sep  95  2
2014 Aug  2900  1
2014 Jul  40  2
2014 Apr  2407  12
2014 Mar  270  19
2014 Feb  219  8
2014 Jan  1503  16
2013 Dec  21  2
2013 Nov  609  2
2013 Oct  241  3
2013 Sep  10  1
2013 Aug  29  3
2013 Jul  202  1
2013 Apr  43  6
2013 Mar  1652  10
2013 Feb  275  4
2013 Jan  247  2
2012 Nov  24  2
2012 Oct  400  10
Tag Cloud
Interested in our services? Still not sure about project details? get a quote