2 Ways of Partition Software Back-End into Modules for Functional Testing

Functional testing is performed not only while checking front-end of an application, but during back-end testing as well.

Functional tests of an application server databases have their specific features and methods. Those who perform web site testing, desktop testing and mobile testing find it useful to divide the software back-end into functional modules and check them individually.

But it may be hard to perform the partition for novice testers.

One May Use Such Methods To Divide a Software Back-End into Functional Modules:

1. To determine main functions of the tested software and basing on them perform the partition. For example, a program allows booking flight tickets, consulting flight schedules and seeing the weather forecasts for various regions. So, the program may be divided into 3 modules. One module will comprise triggers, stored procedures and parts of the databases that are involved in executing one function, for instance, booking flight tickets.
2. To break the program back-end into modules basing on the data flows. In this case one should make a request or call a function in the front-end and watch what stored procedures and tables are addressed in the back-end. They will make up a module for functional tests.

A software testing company frequently uses these methods, as many specialists in mobile application testing, desktop testing and web site testing consider them efficient.

Source: QATestlab