Hi all,
> From: [email protected] > [mailto:[email protected]] On Behalf Of Zheng, Jeff > Sent: Friday, June 10, 2011 5:43 AM > To: [email protected] > Subject: [Meego-qa] Test type change and impact on MCTS > > > > > Hi, > > > > I found new test type has been changed. So it seems to be time that > > MCTS also need to change to fix bug 17877. > > > > But I still have one issue: Some test suites are heavily dependent on > > testlink to export tests.xml. But currently testlink does not support > > new test type (bug 17768). Directly change tests.xml needs much > efforts > > and lead to inconsistence for those test suites. > > > > Can we change for those unimpacted test suites first? I don't prefer > to > > it. > > > > Any suggestion? Can we change tests.xml by manual, or wait for bug > 17768 > > got fixed? > > > > Bests > > Jeff > > I would like to raise this topic again as Jeff had no feedback until now and there is no real progress regarding the submitted bugs: 17768 Test types update in tl.meego.com 17877 Test types update in MCTS 18365 Test types update in Handset UX 18366 Test types update in MNTS 18368 Test types update in Meego SDK To me, adding new test types in testlink (tl.meego.com) first without modifying the existing ones seems to be a good approach. This should avoid inconsistencies and thus testlink will remain compatible with all the Meego test suites whatever the test types used. Moreover new test types will be available for users when creating or updating a test case in testlink. New test types to be added are listed hereafter (7): - Functional positive - Functional negative - Security - Reliability - Performance - Maintainability - Portability Does this approach make sense? Any ideas or suggestions are appreciated... Thanks Christophe _______________________________________________ MeeGo-qa mailing list [email protected] http://lists.meego.com/listinfo/meego-qa
