Ok, a broad topic, I know, but I would like to see what aspects of QA people actually incorporate into their development cycles and the cost/benefit of the different systems. As a QA lead, I have always had to establish CI, unit tests and eventually automated regression. But the trick is to get the agile teams to understand these quality measures, see their value and incorporate it into the definition of done. It really stinks when a team says a sprint is 'done' then another team has to run through weeks of regression testing or something.
Here at IBM we have good CI and unit testing and are just getting the automated blackbox test systems into place. The challenge will be to actually use them. Any advice?
Thanks for your thoughts.
Tags:
At AgilePhilly, we have been Promoting Agile Ideas since 1776
AgilePhilly is a not-for-profit user group of volunteers in the Philadelphia area dedicated to better software development practices.
Meetings are monthly. Get meeting reminders by joining here.
Our attempt with the group is to provide an environment where you can exchange ideas and meet with individuals involved in agile community.
© 2024 Created by Ravindar Gujral. Powered by