Testing the CML

Because the Corporate Media Library (CML) application was developed for a fictional corporation, it will not be tested in a natural usage environment. Until it is, it won't be known how well the CML application performs and scales. To this end, there are a number of tests that could be carried out, as follows:

• Beyond using the current FmLib database, an even larger library-materials dataset was used during development to test scalability. This test helped identify slowdown locations, such as when the catalog of library items is displayed.
• Simultaneous use by a number of library users, perhaps even individuals recruited for the task given access to the CML application specifically for testing.
• Automatic stress tests can be created and run. Automated tests, such as "client emulation", are best for producing scalability data because they can be performed at times when users aren't using their computers, such as in the middle of the night. A disadvantage of this type of test is that it does not detect user-interface defects, for example, inconsistent navigation choices or poor aesthetic design. Automated tests are also are limited in their ability to detect slow application performance.

Results from these tests would be used not only to correct and streamline the CML application's inherent functioning — its user interface for example, or its internal interactions and data transfer operations — but also to determine the best physical and logical configuration in which to install its components.