Hi Excellent questions. I have next to none answers to them but I'll throw in some additional questions/comments
On Wed, 2011-01-19 at 13:40 +0200, Sievi Kari wrote: > Hi, > > I need up-to-date information about Handset and Netbook UX test assets for > MeeGo 1.1 and 1.2 > > Hopefully you can help me with my questions... > > 1. Test asset for Handset UX testing: > http://wiki.meego.com/Quality/TestSuite/handset-test-suite > I would like to see link to source codes and also when the table is updated. > > 2. Should I use TestLink to download test cases? > "Test Cases are designed by QA owners based on existing features and which > have been approved from testability point of view. Test Cases itself are > stored to TestLink tool. Common Test Case Template is used when designing > test cases." > http://wiki.meego.com/Quality/Plans/1.1_Handset_UX_TestPlan#Test_Cases Where is testlink for MeeGo located and can I access it? Are test packages being build in obs from those? > 3. Handset UX Test Suite repository is here > http://meego.gitorious.org/meego-quality-assurance/handset-ux-tests That is > great! > But I found a similar repository for Netbook > http://meego.gitorious.org/meego-quality-assurance/mnts and that is empty. > Now the question is that what is the difference between Handset and Netbook > profiles? Can I use the same test suite for both? > > 4. What is the coverage of handset test suite? > http://wiki.meego.com/Quality/Plans/1.1_Handset_UX_TestPlan#Coverage I'll > need this information in test planning. > > 5. What is the diff between testkit-lite and testrunner-lite? Can I use > testrunner-lite to execute Handset and Netbook test suites? > http://wiki.meego.com/Quality/Netbook_Test_Suite_and_Utilities#Testkit > > 6. I have planned to setup my local OTS worker and execute Handset and > Netbook UX test suites. How OTS is supporting testkit-lite? > This testkit-lite is something that at least I haven't even seen in action so I don't know that much about it. I would guess it won't work too well in test automation (OTS) unless someone is actively maintaining it and making the needed changes to match the evolving test-definition. This is actually bit of an problem. If some tests are written for testkit-lite and it uses some weird/out-of-date test-definition we'll soon have at least 2 test suites that are incompatible with each other. IMO we should stop doing this duplicate work that will only lead to fragmentation and problems with tests and start using the same tool chain for all tests. So pretty please people, let's start working together. -Timo > Hopefully someone could help me :) > > Br, > > Kari Sievi > _______________________________________________ > MeeGo-qa mailing list > [email protected] > http://lists.meego.com/listinfo/meego-qa _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
