NameDateSize

..03-Oct-201821

h_funcs.subrH A D22-Dec-20163.4 KiB

h_tools.cH A D12-Jan-20177.3 KiB

READMEH A D18-Aug-2016891

t_create.shH A D18-Aug-20163.9 KiB

t_devices.shH A D18-Aug-20162.2 KiB

t_dots.shH A D18-Aug-20162.3 KiB

t_exec.shH A D18-Aug-20162 KiB

t_link.shH A D22-Dec-20164.8 KiB

t_mkdir.shH A D18-Aug-20164.8 KiB

t_mknod.shH A D07-Mar-20173.8 KiB

t_mount.shH A D22-Dec-20164.5 KiB

t_pipes.shH A D18-Aug-20161.9 KiB

t_read_write.shH A D18-Aug-20162.9 KiB

t_readdir.shH A D07-Mar-20173.5 KiB

t_remove.shH A D22-Dec-20163.5 KiB

t_rename.shH A D18-Aug-20168.6 KiB

t_renamerace.cH A D07-Mar-20172.2 KiB

t_rmdir.shH A D18-Aug-20165.6 KiB

t_setattr.shH A D18-Aug-20165.9 KiB

t_sizes.shH A D22-Dec-20164.3 KiB

t_sockets.shH A D18-Aug-20162 KiB

t_statvfs.shH A D22-Dec-20162.3 KiB

t_symlink.shH A D18-Aug-20163.6 KiB

t_times.shH A D18-Aug-20164.9 KiB

t_trail_slash.shH A D18-Aug-20162 KiB

t_truncate.shH A D18-Aug-20162.2 KiB

t_vnd.shH A D28-May-20173.3 KiB

t_vnode_leak.shH A D22-Dec-20162.5 KiB

README

1The tests in this directory where written at the same time tmpfs was
2developed.  This is why, if you follow the order of tests in the Atffile,
3you will notice that they start checking the most basic things and end
4checking the less common ones.  Furthermore, tests try not to use features
5tested by further tests in the lists.
6
7However, the above is not the most appropriate testing procedure when you
8have a working file system because some separation in test programs does
9not make sense afterwards.
10
11Many of the tests here are applicable to any file system.  They should be
12refactored to be reusable on any mounted file system, which could also
13remove the need to do the mount/unmount steps in each and every test case.
14
15Possibly take a look at the file system tests in FreeBSD.  They seem to be
16much more complete, even though they are written in Perl and therefore not
17directly usable.
18