Date: Sat, 2 Mar 2019 11:38:24 -0800 From: "Enji Cooper (yaneurabeya)" <yaneurabeya@gmail.com> To: Alan Somers <asomers@FreeBSD.org> Cc: src-committers <src-committers@freebsd.org>, svn-src-projects@freebsd.org Subject: Re: svn commit: r344727 - projects/fuse2/tests/sys/fs/fuse Message-ID: <DBC87309-889A-4E6C-8D58-58107304F557@gmail.com> In-Reply-To: <201903021628.x22GSTTV073206@repo.freebsd.org> References: <201903021628.x22GSTTV073206@repo.freebsd.org>
index | next in thread | previous in thread | raw e-mail
> On Mar 2, 2019, at 08:28, Alan Somers <asomers@FreeBSD.org> wrote: > > Author: asomers > Date: Sat Mar 2 16:28:29 2019 > New Revision: 344727 > URL: https://svnweb.freebsd.org/changeset/base/344727 > > Log: > fuse(4) use a global environment check. > > This is marginally faster than using an environment check in each test case. > Also, if the global check fails then all of the tests are skipped. Oddly, > it's not possible to skip a test in any other way. I used incorrect terminology in my previous description, so I want to clarify my previous points. * SetupEnvironment(..) is for test programs [1]. * SetUp(..) [test fixture] is for test cases. All of these setup APIs have analogs, i.e., teardown APIs. In the next version of GoogleTest, they are adding an API called `SetUpTestSuite(..)`, which will allow one to save state common in a test suite, instead of having to do it per test case. The new API makes sense for long running setup/teardown routines, like initializing a database (which a test suite will use) or network server, from scratch. Cheers! -Enji 1. This API isn’t documented on GitHub; I’ll submit a PR for it.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DBC87309-889A-4E6C-8D58-58107304F557>