Expert QA & Testing
for High-Quality Software Performance

Functional Testing

Functional testing.

We execute functional testing to ensure that the application functionalities are in accordance with the requirement specification. It is, in reality, black box testing and does not delve into the details of the application source code. When carrying out functional testing, the user-friendliness of the important functions of the application remain our strong focus.

For functional testing, we use either manual testing or automation tools however, functionality testing would be easier using manual testing only.

Functional testing typically involves six steps:

• The definition of functions that the software is expected to perform.
• The creation of input data based on the function's specifications.
• The determination of output based on the function's specifications.
• The execution of the test case.
• The comparison of actual and expected outputs.
• Check whether the application works as per the client's need.

Thus, functional testing includes the following testing types:

• Unit testing: also a module level testing, checks if individual modules work properly.
• Integration testing: verifies that the functions responsible for the interaction between different modules work properly.
• System testing: examines the entire functionality of the system on the whole.
• User acceptance testing (UAT): done after the successful completion of unit, integration and system testing and is performed by the end user or the client prior to moving the software app to the production environment.

Functional testing also includes:

• Smoke testing: this is done after the release of each build to ensure that the software is stable and has not impacted any important functionalities.
• Sanity testing: generally done after smoke testing, this is run to verify that every important functionality of an application is working as intended, both by itself and combined with other components.
• Regression testing: this is an important phase of the testing activity and it ensures that modifications done to the codebase (new code, debugging strategies, etc.) do not interfere with the functions that already exist or incite any instability.

Regression testing is required when there is a:

• Modification in requirements and accordingly, the code.
• Addition of a new feature.
• Defect fixing.
• Performance issue fix.

Effective regression tests can be done through the selection of the following test cases:

• Test cases having frequent defects.
• Functionalities which are more visible to the users.
• Test cases which verify core features of the product.
• Test cases of functionalities which has undergone more and recent changes.
• All integration test cases.
• All complex test cases.
• Boundary value test cases.
• A sample of successful test cases.
• A sample of failure test cases.

Beta/usability testing

In this phase, our clients test the product in a production environment. This stage is essential to know the customer's comfort level with the interface. We use their feedback to make further improvements to the system.