NetBSD/tests/fs/tmpfs
jmmv e834f57d5e Properly mark some test cases as having a cleanup routine. Stupidity of
the API?  Most likely; will revise it.

Fixes atf-run breaking when running t_psshfs.  This does not resolve the
underlying issue though, which is atf-run getting confused trying to
unmount the temporary mount point by itself (I think).  (I'm now wondering
if atf should be bothering about unmounting stuff at all.  Maybe not. It is
a tricky and uncommon thing.)
2010-07-05 16:27:08 +00:00
..
Atffile Remove a test (that a created directory had a predictable inode number) 2010-06-07 03:43:50 +00:00
h_funcs.subr
h_tools.c
Makefile Remove a test (that a created directory had a predictable inode number) 2010-06-07 03:43:50 +00:00
README
t_create.sh Use atf_check to su in a couple cases, to make the test failure 2010-06-07 03:39:41 +00:00
t_devices.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_dots.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_exec.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_link.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_mkdir.sh Use atf_check to su in a couple cases, to make the test failure 2010-06-07 03:39:41 +00:00
t_mknod.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_mount.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_pipes.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_read_write.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_readdir.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_remove.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_rename.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_renamerace.c Add a test case for PR kern/36681 demonstrating how easy it is to 2010-07-04 12:43:23 +00:00
t_rmdir.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_setattr.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_sizes.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_sockets.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_statvfs.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_symlink.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_times.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_trail_slash.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_truncate.sh atf-0.9 introduces an use.fs test-case property to allow tests to write to 2010-06-04 08:39:40 +00:00
t_vnd.sh Properly mark some test cases as having a cleanup routine. Stupidity of 2010-07-05 16:27:08 +00:00
t_vnode_leak.sh Properly mark some test cases as having a cleanup routine. Stupidity of 2010-07-05 16:27:08 +00:00

The tests in this directory where written at the same time tmpfs was
developed.  This is why, if you follow the order of tests in the Atffile,
you will notice that they start checking the most basic things and end
checking the less common ones.  Furthermore, tests try not to use features
tested by further tests in the lists.

However, the above is not the most appropriate testing procedure when you
have a working file system because some separation in test programs does
not make sense afterwards.

Many of the tests here are applicable to any file system.  They should be
refactored to be reusable on any mounted file system, which could also
remove the need to do the mount/unmount steps in each and every test case.

Possibly take a look at the file system tests in FreeBSD.  They seem to be
much more complete, even though they are written in Perl and therefore not
directly usable.