It is an essential part of the software development cycle to have REAL-LIFE, BUSINESS UESER, BETA TESTERS use the newly deployed web applications as part of a “soft-launch.”

Experienced software architects and developers, you already know this truth: non-technical users, or even highly technical user that were not involved in the software development process, ALWAYS interact with the UI in ways that the developers failed to anticipate. Examples include typing ENTER vs. clicking submit, alternate paths and entry points to the web app, bookmarking a page requiring session state…. the list goes on.

It has been my experience that there exists a POWERFUL temptation for clients to complete testing in-house, in the hopes that the web application will be “perfect” upon release to their users.

Big no-no. Triple no-no-no.

I don’t have enough toes and fingers on which to count the instances of “emergencies” that have resulted from client staff and developer testing only.

More later…