On 06/15/2011 03:37 PM, Pelkonen Tuomo wrote:
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
The quality criteria says: The test asset be run with testrunner-lite
I'm wondering that if the tests.xml includes all the test cases, also manual,
how can it be run with testrunner-lite?
I have to say that this rule is hard to implement...It actually hopes
asset owner to do it himself.
How to run MCTS, please refer to
http://wiki.meego.com/Quality/TestSuite/MCTS/Run_MCTS. Feel free to
modify/add if you like.
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.
This packaging style was a design to provide support for multiple platforms -
not going to details in here :)
Does the package need to be named -tests to be runnable by testrunner-lite and
OTS?
As I know, testrunner-lite just read /usr/share/<test package>/tests.xml
and execute the un-filtered cases. Anyway, it's best that you rename
back to -tests to avoid potential conflict.
Any more comments?
Bests
Jeff
_______________________________________________
MeeGo-qa mailing list
[email protected]
http://lists.meego.com/listinfo/meego-qa
