Hi Damon, I've been involved in this type of work so much that sometimes it makes my head spin. To echo Will's bravo and also his explanation of the benefits which you are seeming to see yourself. I've also found that being a part of the QA process has helped me to build closer relationships with my engineering/IT team because we are all in the thick of it and I can better see their challenges and pains in this phase of the project.
One of the biggest challenges that I've seen besides resource constraints is both from a testing data point of view as well as a testing/defect management software point of view. First I find it increasingly hard to get the data I need to test the entire interaction even if I'm only doing high level testing. Usually, at least in my experience, because IT/engineering/QA are usually closer physically they can get their hands on this faster and because they are busy don't always pass it along. This is probably also due to the fact that I'm a new part of the process and there is nothing that says get the IA test data so that they can do interface/interaction testing. Secondly I'm usually not set up in or familiar with the software used to manage the defects. There is usually a lag in the time that I get an id/password and the time i've started testing. Then I need to account for understanding the software, and the IT/engineering terms in it that refer to our effort. Obviously once this is set up and I've used the software a few times I'm good to go. Hope this helps! Lis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=34881 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
