INTEGRATION TEST

During integration, test can be done using the “big bang” approach however this has been proven to be a method that is very ineffective as problems are not easily isolated and a systematic approach can not be implemented properly.

Instead a more systematic approach such as top-down integration can be applied for testing. This way, modules are integrated by moving downward through the control hierarchy, beginning with the main control module (main program). On top of it, regression testing will be done. After each new module has been added, some execution test can be redone to ensure that changes have not propagated unintended side effects.

The integration process is performed in a series of five steps:

1. The main control module is used as a test driver and stubs are substituted for all components directly subordinate to the main control module.
2. Depending on the integration approach selected (i.e. depth or breadth first), subordinates stubs are replaced one at a time with actual components.
3. Tests are conducted as each component is integrated.
4. On completion of each set of tests, another stub is replaced with real component.
5. Regression testing may be conducted to ensure that new errors have not been introduced

In our program, we identify the log in form as the main control module while the rest of the modules are subordinate to it. This is because in order for one to use the program, one has to log in before being able to access anything else.

Firstly, we integrate it with the client database as it is one of the simplest module of the whole program. Theoretically, there should be no interference as they are independent modules. The log-in form will only allow the user to access the rest of the other modules. However, individual testing will be repeated after this integration.

Next, the integration of the goods form. This process would be similar to the previous process. Again, individual testing will be repeated.

The integration of the scheduling should be trickier. This is due to the fact that the schedule form will need to access the goods form’s database and update it. This part may affect the good’s form. After each test, the database needs to be checked if updating is done properly.

<< Back to Testing