Testing Results and Future Plans

The testing executed thus far were the tests for the main website functionalities: Adding/Updating/ Deleting Paintings, Events and News. Further for the remaining modules will be conducted at a later date, as well as system wide test in the production environment.

Testing Results
Most of the unit test results were positive. The developers took great care in programming and testing each module before releasing the version to be uploaded into the production environment. The unit tests were approximately 85 percent successful. Various team members reported a good experience when testing the website. The good experience was measured in terms of: (1) bug-free code and (2) intuitive design. There were many challenges to overcome when the website was uploaded to the production server, however. Problems such as build errors, component problems, etc had to be overcome. Judy saw some of these problems firsthand during the meeting on April 22. The consequences of such challenges were: delay in modules-integration tests, coding conflicts and flawed website presentation. Most of these problems are now fixed.

Future Plans
The tech lead, Alberto, is going to become more familiar with the production environment to avoid future production environment problems. Barry has just granted him full access to deploy uploaded files and modify current files. The goal is to avoid the consequences listed above in the future tests. The next round will begin with unit tests for the remaining modules and re-testing of previously coded modules. Once these tests are executed, the system-wide tests will start. The

testers will include the team, friends of the team members, Judy and Judys friends. Unit tests are scheduled to start on May 1. System-wide tests are scheduled to start on May 8.