Hi Juan Pablo,
For me the workflow that you propose makes a lot of sense from a QA
perspective. Let's ensure that the addition of 2 new status does not imply
extra work: let's automate the transition from "Ready for testing" to "Ready
for review" and from "Resolved" to "Closed".
2009/11/18 Juan Pablo Aroztegi <[email protected]>
> But now we have the Continuous Integration factor as well. So need to
> differentiate between "CI testing" and "Manual
> testing/verification/review".
> * The CI moves an issue from "Ready for testing" to "Ready for review".
>
Is there a list of all the build and smoke tests that are performed before
moving from "Ready for testing" to "Ready for review"?
Thanks.
Rafa
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Openbravo-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openbravo-development
