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 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? br, Tuomo Pelkonen -----Original Message----- From: Jeff Zheng [mailto:[email protected]] Sent: 15. kesäkuuta 2011 9:58 To: Pelkonen Tuomo Cc: [email protected] Subject: Re: [Meego-qa] No tests.xml in mwts packages On 06/15/2011 02:43 PM, Tuomo Pelkonen wrote: > >>> Just found that there is no tests.xml in mwts packages, furthur >>> checking >>> shows that all mwts assets move tests.xml to tests-all.xml and don't >>> include tests-all.xml into mwts packages. >>> >>> Since tests.xml is reserved name for mcts test suites, I reported a >>> critical bug 19174 to track this issue. Please fix it as soon as >>> possible! >>> >> Hello Jeff, >> It would be too late to discover the issue after it entered into >> MCTS. To avoid such obvious mistakes, how about we define some >> quality criteria that each test suite owner should follow before they >> submit merge request? > > Hello Elva and Jeff, > > This change is something that MWTS test assets needed to be executable > in OTS test automation properly. What was a mistake obviously, is that > it was put part of official MCTS release before being properly > discussed in meego-qa mailing list. I'm very sorry about this :/ > > What kind of problems have you encountered due to this change? Has the > tests.xml been used in some other use than test automation? Anyway, > the old tests.xml:s were not designed to be a test plan, but only to > represent all available test cases. That's the reason for the file > name case in the first place. tests.xml defines all test cases in the test asset, includes both manual and auto test cases. test plan, or 'test set', is a collection of test cases from several test assets. I don't think that the test paln/'test set' file will be in specific test asset package (like mwts-ofono packages). Though I'm open to have a 'test set' package to define such test plan/'test set', refer to http://lists.meego.com/pipermail/meego-qa/2011-June/001860.html Bests Jeff _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
