On Thu, Mar 09, 2017 at 06:46:48AM +0000, David Howells wrote: > Eryu Guan <eguan@xxxxxxxxxx> wrote: > > > There's a "ADDING TO THE FSQA SUITE" section in README file, basically > > it's telling you to use './new' script to generate new test template. So > > based on what type of new test you're going to create, you could run: > > > > ./new generic # new generic test > > ./new xfs # new xfs test > > ./new ext4 # new ext4 test > > ./new shared # new shared test > > ... > > > > It finds the first free seq number and creates test template and a > > default .out file in tests/<type> dir and add a new entry in > > tests/<type>/group file. You could just edit the template and update > > the .out file with expected output from the test run. > > Yes, I'd spotted the ./new script, but it's not as simple as that since shell > scripts can't call system calls directly. A normal way we take for fstests is adding new syscall support to xfs_io first, then writing new tests based on it, as some other new syscalls/utilities do, e.g. set|get_encpolicy were added to xfs_io in January to set|get encryption policy for ext4 encryption testing. Thanks, Eryu -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
