Client Testing

Client testing is an important part of the application-delivery process. Without this, Vshift would be placing a lot of faith in its own testing process. While Vshift's testing was thorough, things can sometimes be deceiving when developers test their own applications. Often developers will have very powerful machines with all of the necessary software and plug-ins to ensure successful development. This power is liable to hide many application shortcomings that can be detected by client testing. Also, application developers know what to expect when screens are shown often they do not think to test an application in ways that a first-time user will.

Client Comments

Through the weekend, the MonkeyTongue sales team members tested the application using their notes and checklists from the earlier walk-through. MonkeyTongue formulated their comments into the following memo to Vshift.

Change Requests

MonkeyTongue staffers put together a few change requests they thought would make the application better. The first request was from the MonkeyTongue CEO (Figure II-4.27). He wanted some of the buttons to be changed from "Done" to "Continue." Since he felt this was required for logical use of the application, Vshift will make the changes in this phase.

Figure II-4.27. The first change request.

The next change request that came in was also from the CEO, requesting that the MonkeyTongue logo be added to the application (Figure II-4.28). He marked the change as suggested, but since it would be very easy to add, the Vshift design team quickly added it to the background of the application.

Figure II-4.28. The second change request.

The final change came in from the sales team (Figure II-4.29). This change was discussed in the comments that it sent earlier. The sales team felt the change could wait until the next version of the application.

Figure II-4.29. The final change request.