Hello devs and testers. I wanted to throw out my .02 on testing, and give my thoughts on good practices as far as tester/dev interaction goes.
One of the biggest problems I've seen on both sides of the dev/tester line is that tester's really need to know what the intended purpose or functionality is of the things that they're testing. If widget Y is meant to blow up, the tester should be aware of that before (s)he tests the application, otherwise chances are they will report said widget as a bug, and thus eat up their testing time, and dev time chasing their tails.
What I'd like to see more than bug reports (which are needed as well), is a comprehensive, dynamic list of intended functionality within the new MxO on QA. The more information that you (SOE) can provide your testers on intended functionality, the more efficient your testers and QA/devs will become.
One of the biggest problems I've seen on both sides of the dev/tester line is that tester's really need to know what the intended purpose or functionality is of the things that they're testing. If widget Y is meant to blow up, the tester should be aware of that before (s)he tests the application, otherwise chances are they will report said widget as a bug, and thus eat up their testing time, and dev time chasing their tails.
What I'd like to see more than bug reports (which are needed as well), is a comprehensive, dynamic list of intended functionality within the new MxO on QA. The more information that you (SOE) can provide your testers on intended functionality, the more efficient your testers and QA/devs will become.