5.0 Integration Testing

Due to time constraints we were unable to do as much integration testing as we had initially planned. Many of the components in the IFESS system such as the movie viewer, media player, and internet browser are third party software components, as such they did not require the same extensive integration testing as the others. Although these were tested, the majority of our focus was on the newly created and implemented modules such as Food and Billing

Integration testing was performed using a bottom-up approach. As modules were completed, they were merged into the IFESS framework...

5.1 Test Cases:

Modules were added in the following order:
Module
Description
Comments
Tester
Information Update  The interface with the backend database. The module also interfaces with the GUI.  This was the first module integrated.  Myran "The Machine" Sathasivham 
Billing  Interfaces with the back end datastore as well as the food and movie modules.  The integration of this module was smooth.  Johnny Ho 
Food  Interfaces with the backend database, the GUI, and the billing module.  The integration of this module was smooth.  Jordan Hull 
Movies  Interfaces with the backend datastore, the GUI, and the billing module.  The integration of this module was smooth.  Johnny Ho 
Music  Interfaces with the backend database and the GUI.  The integration of this module was smooth.  Jordan Hull 
In-Flight Information  Interfaces with the backend database and the GUI.  No testing has been done on the integration with Fly-By-Wire's ground system.  Myran "The Machine" Sathasivham 
Internet  Interfaces with the backend database and the GUI.  The integration of this module was smooth.  Jordan Hull 
Games  Interfaces with the backend database and the GUI.  The integration of this module was smooth.  Johnny Ho 
Help  Has no internal logic and does not interface with any modules besides the GUI.  The integration of this module was smooth.  Jordan Hull 
GUI  The top level component of the system.  The integration of this module was smooth.  Johnny Ho 

5.2 Integration Summary:

As modules were added smoke tests were performed on the new component and the current system state to ensure that adding the new module hadn't caused any problems with exisisting functionality.