Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 2 Mar 2019 12:31:48 -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:  <B7A7D88B-044D-4DFF-A21A-76F968DE3294@gmail.com>
In-Reply-To: <DBC87309-889A-4E6C-8D58-58107304F557@gmail.com>
References:  <201903021628.x22GSTTV073206@repo.freebsd.org> <DBC87309-889A-4E6C-8D58-58107304F557@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

> On Mar 2, 2019, at 11:38, Enji Cooper (yaneurabeya) =
<yaneurabeya@gmail.com> wrote:
>=20
>=20
>> On Mar 2, 2019, at 08:28, Alan Somers <asomers@FreeBSD.org> wrote:

=E2=80=A6

>> Oddly, it's not possible to skip a test in any other way.

I want to highlight this sentence a bit.

It=E2=80=99s possible to skip test cases by prefixing them with =
`DISABLED_` =E2=80=94 which you can then ignore when rerunning the test =
program via `=E2=80=94gtest_also_run_disabled_tests`. However, you can =
actually skip tests at runtime via the `GTEST_SKIP()` macro, as well, =
which in combination with `SetupEnvironment(..)` is probably the most =
correct way to handle prerequisites not being met at runtime.

HTH,
-Enji=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B7A7D88B-044D-4DFF-A21A-76F968DE3294>