NetBSD/tests/fs/tmpfs
maya b42dccbff0 Use sysctl -n rather than parse the output.
From Ngie Cooper in PR bin/51870
2018-01-17 00:23:17 +00:00
..
Makefile
README
h_funcs.subr
h_tools.c - Add inttypes.h #include for PR* macros. 2018-01-17 00:22:29 +00:00
t_create.sh
t_devices.sh
t_dots.sh
t_exec.sh
t_link.sh
t_mkdir.sh
t_mknod.sh
t_mount.sh
t_pipes.sh
t_read_write.sh
t_readdir.sh
t_remove.sh
t_rename.sh
t_renamerace.c
t_rmdir.sh
t_setattr.sh
t_sizes.sh Use sysctl -n rather than parse the output. 2018-01-17 00:23:17 +00:00
t_sockets.sh
t_statvfs.sh Use sysctl -n rather than parse the output. 2018-01-17 00:23:17 +00:00
t_symlink.sh
t_times.sh
t_trail_slash.sh
t_truncate.sh
t_vnd.sh Do not assume anything about the pseudo-disklabel of a completely zeroed 2017-03-23 08:18:17 +00:00
t_vnode_leak.sh Use sysctl -n rather than parse the output. 2018-01-17 00:23:17 +00:00

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.