ubixos / contrib / netbsd-tests / fs / tmpfs /
..
README More Cleanup 7 years ago
h_funcs.subr More Cleanup 7 years ago
h_tools.c More Cleanup 7 years ago
t_create.sh Sync 6 years ago
t_devices.sh Sync 6 years ago
t_dots.sh Sync 6 years ago
t_exec.sh Sync 6 years ago
t_link.sh Sync 6 years ago
t_mkdir.sh Sync 6 years ago
t_mknod.sh Sync 6 years ago
t_mount.sh Sync 6 years ago
t_pipes.sh Sync 6 years ago
t_read_write.sh Sync 6 years ago
t_readdir.sh Sync 6 years ago
t_remove.sh Sync 6 years ago
t_rename.sh Sync 6 years ago
t_renamerace.c More Cleanup 7 years ago
t_rmdir.sh Sync 6 years ago
t_setattr.sh Sync 6 years ago
t_sizes.sh Sync 6 years ago
t_sockets.sh Sync 6 years ago
t_statvfs.sh Sync 6 years ago
t_symlink.sh Sync 6 years ago
t_times.sh Sync 6 years ago
t_trail_slash.sh Sync 6 years ago
t_truncate.sh Sync 6 years ago
t_vnd.sh Sync 6 years ago
t_vnode_leak.sh Sync 6 years ago
README
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.