svn commit: r344715 - in projects/fuse2: etc/mtree tests/sys/fs tests/sys/fs/fuse

[Alan Somers]

On Fri, Mar 1, 2019 at 5:28 PM Enji Cooper <yaneurabeya at gmail.com> wrote:
>
>
> > On Mar 1, 2019, at 15:53, Alan Somers <asomers at freebsd.org> wrote:
> >
> > Author: asomers
> > Date: Fri Mar  1 23:53:05 2019
> > New Revision: 344715
> > URL: https://svnweb.freebsd.org/changeset/base/344715
> >
> > Log:
> >  Begin a fuse(4) test suite
> >
> >  It only tests the kernel portion of fuse, not the userspace portion (which
> >  comes from sysutils/fusefs-libs).  The kernel-userspace interface is
> >  de-facto standardized, and this test suite seeks to validate FreeBSD's
> >  implementation.
> >
> >  It uses GoogleMock to substitute for a userspace daemon and validate the
> >  kernel's behavior in response to filesystem access.  GoogleMock is
> >  convenient because it can validate the order, number, and arguments of each
> >  operation, and return canned responses.
> >
> >  But that also means that the test suite must use GoogleTest, since
> >  GoogleMock is incompatible with atf-c++ and atf.test.mk does not allow C++
> >  programs to use atf-c.
> >
> >  This commit adds the first 10 test cases out of an estimated 130 total.
> >
> >  PR:        235775, 235773
>
> Hi Alan!
>     Could you please use SetupEnvironment to ensure that /dev/fuse exists and is accessible? This is something I needing to be done with the zfsd tests too, IIRC.
> Thanks so much :)!!
> -Enji

What's the advantage to doing it that way as opposed to using the
regular SetUp function?

-Alan