The fact that the results of a first round of testing is due before the completion of the product has also taught us that testing can be incremental in nature. Many of us have the linear concept of a product lifecycle, where testing occurs only after the complete implementation of all the features. However, through preparing this first version of the Verification and Validation Results document, we have learned the usefulness of an iterative development-testing scheme. 5.0 Outcome of Acceptance Test and Delivery Acceptance testing and delivery has not yet been performed. In the functionalty test for the eMoo Simulator, the initial login gave problems with some passwords.
Case sensitivity is an issue.
This will be resolved by notifying the users of the case sensitivity. In the help component it was difficult to determine whether the softlinks functioned correctly due to the length of the help information at the time. The following tables contain the results of the implementation of the test plans. Each test contains the name of the test, the date it was performed, the name of the tester, a description of the test, the expected results, the actual results, and an indication of whether the test passed or failed. The username should be passed through as well.