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
package.
Again I'd like to repeat that one tests.xml rule defined in release
criteria and guideline for a long time:
http://wiki.meego.com/Quality/TestSuite/MCTS/MCTS_Release_Process
http://wiki.meego.com/Quality/TestSuite/MCTS/MCTS_Development_Guideline
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.
Bests
Jeff
_______________________________________________
MeeGo-qa mailing list
[email protected]
http://lists.meego.com/listinfo/meego-qa
