Hi Jeffrey,
On 02/13/09 08:48, jeffrey huang wrote: > Hi, William and Jan, > > I'd like to suggest that can we give up the liborchestrator test > suite? I am based on following reason: > > liborchestrator test suite based on 2 test driver: > - disktest > - kbdtest > > 1. disktest is unnecessary when AI manifest processing was > implemented, some of the features could be covered by AI testing and > TD testing I tend to agree. We have recently discussed this with William and he pointed this out as well - the same level of test coverage can be accomplished by combination of TD and AI - William suggested to enhance orchestrator for testing purposes by specifying set of checkpoints in which we could terminate the process and inspect test results. > > 2. kbdtest is plan to be replaced with G11n test driver which would be > delivered with G11n module proposed by globalization team. kbdtest is definitely out of date and thus useless. As you pointed out, the plan was to replace it with the one delivered with G11n module. However, no ETA is available at the time being, so the plans might need to be accommodated - stay tuned :-). Thank you, Jan > > 3. And the current test cases we could implemented and features we > could covered are quite limited. > > I came out above conclusion by tracking following bugs and email > thread for "code review request 5656": > > bug 6193 Needs to integrate test binaries to package when build > slim_source > bug 5644 TD and TI test drivers should be built as part of full build > of source gate > Bug 3112 liborchestrator test driver should be enhanced to address QA > requirements > > -- > Great Thanks & Best Regards > > --- > Jeffrey Huang SWAN: x51683, Ext: 0086-10-62673683 > Solaris QE Group Email: jeffrey.huang at sun.com > China Engineering & Research Institute, Sun Microsystems > 7/F Chuang Xin Plaza, Tsinghua Science Park, Beijing China >
