On 06/27/2013 09:09 AM, [email protected] wrote: > Hi! >>> Signed-off-by: Sedat Dilek<[email protected]> >>> --- >>> runtest/ipc | 60 >>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>> 1 file changed, 60 insertions(+) >> NAK. Duplication is generally a bad idea. >> This have the side effect of running the same tests twice for people >> that run ipc and syscalls test scenarios. > Hmm, this is a valid point. > > Thinking of the ideal way, it may be more data driven framework with a > list of all tests anotated with some group labels. I noted this for the > planned testdriver rewrite. >
We can easily support this with existing infrastructure if we add some structure to the test case tags. For instance on runtest/syscalls, one could use: msgctl01_ipc msgctl02_ipc ... Then when calling runltp, one can use -s option to filter tests cases, e.g. ./runltp -f syscalls -s '*_ipc' At Texas Instruments we use following convention for TAG names <AREA>_<SCOPE>_<TYPE>_<ID> ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
