Hi Petr, The frequent change of feature test cases would be perfectly supported by our current Litmus testing strategy.
Saying a feature branch, from which a test run is created, a new test case created in that branch would reflect immediately to that test run :) A generic (not version specific) regression test case may not reflect to the test run immediately because it is always added to a "Master branch". So it will be executed by QAs in Test Runs in either of the scenarios: 1. When next version specific regression test branch created from the latest master regression test branch 2. When manually "synchronize" test cases in version specific regression test branch with master branch. Best wishes, Yifan On Fri, Nov 04, 2011 at 10:06:16AM +0100, Petr Mladek wrote: > Yifan Jiang píše v Pá 04. 11. 2011 v 14:56 +0800: > > The feature branch has no difference with regresstion test branch, so > > if the > > Test Run Admin works as I expected, it will not be a problem. > > I would expect more frequent changes in the feature branch. We have new > features every week. Well, it is questionable. We need more test cases, > so it would be great to get many changes in the regression tests as > well. _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/