From: Subrata M. <su...@li...> - 2008-07-30 13:02:56
|
Hi Rishi, Thanks for noting this down. I was already thinking of looking into such issues in LTP where lots of test cases are not run by default. The reasons for them being: 1) Requires special setup, 2) Some test cases are meant for specific FS types, 3) Some other unknown reasons, which needs to be investigated. Now, here are the options that i would like to envisage: 1) See whether there are any tests under that ltp/testcases/kernel/fs directory which can be integrated to the default ltp run, by making an entry inside runtest/fs command file. If this can be done, then this should be the first place to do it, 2) If they cannot be integrated to runtest/fs as they might require a special setup, the we have the following approach: Create a new command file call runtest/fs_all. This should basically contain a proper documentation saying the special setup required to run these and those tests. You can have a variable=set/unset combination(s) to determine which tests to run and which not to, say: RUN_MONGO=Y, RUN_DMAPI=Y, .... etc, Depending on these values, the tests will be run. But even if these values are set, the script should be able to verify if the setup is complete, else the tests should not be run. Also simplify the setup by giving users the options to know some setup variable/values dynamically. Say, if we are doing a ext4 testing, then the tests will require a ext4 fs to be existing in the test machine. So, set up a variable in the script like: EXT4_PATH_SET=Y EXT4_DIRECTORY_TEST_PATH=/tmp/abcdef .. things like that. Let the user mention the rest, 3) Once that is done, i would like to revive/rewrite the entire ltp/runalltests.sh, which will be then used to run these special tests as well as the default LTP tests. Entries in runalltests.sh can be like: ....... ./runltp <with desirable options> ./runltp -f fs_all .... Things like that. Let me know what you think. Regards-- Subrata On Wed, 2008-07-30 at 15:01 +0530, Rishikesh K. Rajak wrote: > Hi All, > > I was going through the "/root/ltp-full-20080630/testcases/kernel/fs" > directory and i found that there are so many testcases are not running > by default, just want to take care of this activity so that we will > come to know that why we are keeping this filesystem testcase inside > kernel/fs directory and we are not using it, little investigation is > require for this. > > My main aim: Get run all the filesystem related testcases with maximum > number of various argument, so that we can get good coverage of kernel > filesystem testing. > > Some investigation which i did: > Kernel/fs directory is having these many testcases as per the > latest LTP release and only few of the testcases are being run by > "runltp" script. we need to give some special attention to the other > testcase so that we will able to run all the filesystem related > testcase, or we can also write/include new testcase related to kernel > filesystem. > > [root@x445 fs]# pwd > /root/ltp-full-20080630/testcases/kernel/fs > [root@x445 fs]# ls -ltr > total 92 > drwxrwxr-x 2 test brewbuilder 4096 Jun 29 01:49 fs-bench > drwxrwxr-x 4 test brewbuilder 4096 Jun 29 01:49 scsi > drwxrwxr-x 2 test brewbuilder 4096 Jun 29 01:49 racer > drwxrwxr-x 2 test brewbuilder 4096 Jun 29 01:49 mongo > -rw-rw-r-- 1 test brewbuilder 327 Jun 29 01:49 Makefile > drwxrwxr-x 2 test brewbuilder 4096 Jun 29 01:49 linktest > drwxrwxr-x 2 test brewbuilder 4096 Jun 29 01:49 fs_maim > drwxrwxr-x 2 test brewbuilder 4096 Jun 29 01:49 fs_inod > drwxrwxr-x 8 test brewbuilder 4096 Jun 29 01:49 fs_bind > drwxrwxr-x 2 test brewbuilder 4096 Jun 29 01:49 dmapi > drwxrwxr-x 2 test brewbuilder 4096 Jun 29 01:49 acl > drwxrwxr-x 2 test brewbuilder 4096 Jul 30 19:38 acls > drwxrwxr-x 2 test brewbuilder 4096 Jul 30 19:38 fsstress > drwxrwxr-x 2 test brewbuilder 4096 Jul 30 19:38 fs_perms > drwxrwxr-x 2 test brewbuilder 4096 Jul 30 19:38 doio > drwxrwxr-x 2 test brewbuilder 4096 Jul 30 19:38 fsx-linux > drwxrwxr-x 2 test brewbuilder 4096 Jul 30 19:38 ftest > drwxrwxr-x 2 test brewbuilder 4096 Jul 30 19:38 proc > drwxrwxr-x 2 test brewbuilder 4096 Jul 30 19:38 openfile > drwxrwxr-x 2 test brewbuilder 4096 Jul 30 19:38 lftest > drwxrwxr-x 2 test brewbuilder 4096 Jul 30 19:38 inode > drwxrwxr-x 2 test brewbuilder 4096 Jul 30 19:38 stream > drwxrwxr-x 2 test brewbuilder 4096 Jul 30 19:38 fs_di > [root@x445 fs]# > > Please let me know if someone is having some other opinion/plan on > this. > > - Rishi > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ Ltp-list mailing list Ltp...@li... https://lists.sourceforge.net/lists/listinfo/ltp-list |