Act As Though The User Will See Everything You Type

At DailyWTF, a reader offers another object lesson in having clever developer messages, not for public consumption, consumed by the public.

Whereas the article at DailyWTF talks about the hard-coded messages within the application, remember, ungentle reader, that QA also has the chance to enter badness into the system when creating junk data for testing (see Keeping Your Test Data Clean).

Developers need to assume that the impossible error condition will occur (assuming the application even works, that is), and QA needs to assume that the business stakeholders will be stupid enough to use the test environment for demos or for milestone meetings with the client.

Comments are closed.

wordpress visitors