NYCPHP Meetup

[Bill Lovett]

I'm close to finishing an overhaul of a large application and will soon
need to start up the testing, bug fixing, and "oops I forgot about that"
phase. In the past, testing and qa have been handled pretty informally.
They've also been pretty ineffective. Does anyone have suggestions or
how-to stories for how to come up with test plans and procedures without
having the luxury of a dedicated QA department? I'm not so much looking
at things like unit testing as I am more user-related issues, like
making sure an error message appears when it should or confirming that
when a user deletes a database record, it really gets deleted.

-bill