19 years doing it, I can't help but bring it up. Grin.

Two more things from you brought up:

1. Cultivate a UX test savvy QA person. They can see the 13 shades of gray and single pixel alignment issues at 10 paces. Let them do that consistency checking, and support them in getting things resolved.

2. Review the test plans. "Bugs" often live at all parts of the process, and QA will find them in your stuff, too. Fix them there before implementation completes and it "costs" less.

-- Jim
   Via my iPhone

On Aug 25, 2009, at 10:34 AM, Audrey <audcr...@gmail.com> wrote:

I am glad that Jim brought up the QA team. They should have specs,
scenarios or prototypes from which to build test plans. If eng knows
they'll get a bug filed against them, they're more likely to
implement to spec.

Designers should also be brought into the QA cycle to catch visual
problems that a QA team might not see. After being trained on good
bug reporting and process, of course.
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... disc...@ixda.org
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help

Reply via email to