[Meego-qa] No tests.xml in mwts packages
timo.harkonen at digia.com
Wed Jun 15 00:56:04 PDT 2011
On Wed, 2011-06-15 at 10:19 +0300, Jeff Zheng wrote:
> On 06/15/2011 03:06 PM, Pelkonen Tuomo wrote:
> > So should a test plan have different name than tests.xml, for example testplan.xml, to avoid confusion and to separate purpose of these files?
> > http://wiki.meego.com/Quality/QA-tools/Test_plan
> This is another topic. I just prefer to talk about tests.xml in mcts
> Again I'd like to repeat that one tests.xml rule defined in release
> criteria and guideline for a long time:
> > Another thing is, now we have packages named differently than before, there is no -tests package at all. Is it ok to have test packages named like mwts-filesystem-scripts?
> Actually I prefer to have one package per test asset, but it's reality
> that each mwts test asset has several test packages for a long time. I'm
> OK with it.
One of the issues with tests.xml files is the naming. Calling those xml
files test plans seems cause confusion. From automation point of view
those files aren't actually plans, they're instructions how to execute
the test cases. But the files are used in different contexts so from
some point of view it is justified to call them plans.
E.g. If there's a need to do a automated test run with selected cases
from different test assets/packages you can do a test package (e.g.
some-nightly-tests) that contains only the tests.xml file and
dependencies to the used assets/packages. The problem with this is that
if some asset changes the xml in the test set package also needs to be
The issue here has been brought up previously by E-P. He wrote about it
to his wiki page
Anyway this is a real issue and needs to be resolved (ASAP). There's
currently active discussion about the topic in #meego-qa hopefully the
guys participating in it also take the time to follow it up on this
More information about the MeeGo-qa