Home
last modified time | relevance | path

Searched refs:assertions (Results 1 – 25 of 66) sorted by relevance

123

/freebsd-14.2/contrib/googletest/docs/reference/
H A Dassertions.md25 The assertions in this section generate a success or failure directly instead of
46 considered successful only if none of its assertions fail during its execution.
105 Matchers enable assertions of this form to read like English and generate
125 The following assertions test Boolean conditions.
143 The following assertions compare two values. The value arguments must be
156 These assertions work with both narrow and wide string objects (`string` and
222 The following assertions compare two **C strings**. To compare two `string`
263 The following assertions compare two floating-point values.
269 GoogleTest also provides assertions that use a default error bound based on
334 The following assertions enable more complex predicates to be verified while
[all …]
H A Dtesting.md28 [Assertions](assertions.md) used within the test body determine the outcome of
48 [Assertions](assertions.md) used within the test body determine the outcome of
80 [Assertions](assertions.md) used within the test body determine the outcome of
349 [Adding Traces to Assertions](../advanced.md#adding-traces-to-assertions).
366 Similar to assertions, `GTEST_SKIP` allows streaming a custom message into it.
1409 See [Type Assertions](../advanced.md#type-assertions) for more information.
/freebsd-14.2/contrib/googletest/docs/
H A Dprimer.md81 When using GoogleTest, you start by writing *assertions*, which are statements
86 *Tests* use assertions to verify the tested code's behavior. If a test crashes
102 or function by making assertions about its behavior. When an assertion fails,
122 the [`ASSERT_EQ` and `EXPECT_EQ`](reference/assertions.md#EXPECT_EQ) macros to
138 GoogleTest provides a collection of assertions for verifying the behavior of
141 much more. There are even assertions that enable you to verify more complex
142 states by providing custom predicates. For the complete list of assertions
152 use the various GoogleTest assertions to check values.
153 3. The test's result is determined by the assertions; if any assertion in the
479 *unsafe* to use Google Test assertions from two threads concurrently on
[all …]
H A Dquickstart-cmake.md88 // Demonstrate some basic assertions.
97 GoogleTest provides [assertions](primer.md#assertions) that you use to test the
99 and demonstrates some basic assertions.
H A Dquickstart-bazel.md77 // Demonstrate some basic assertions.
86 GoogleTest provides [assertions](primer.md#assertions) that you use to test the
88 and demonstrates some basic assertions.
H A Dadvanced.md7 will show you more assertions as well as how to construct complex failure
14 assertions.
18 See [Explicit Success and Failure](reference/assertions.md#success-failure) in
45 [`EXPECT_PRED*`](reference/assertions.md#EXPECT_PRED) in the Assertions
138 [`EXPECT_PRED*`](reference/assertions.md#EXPECT_PRED) and
141 instead use *predicate-formatter assertions* to *fully* customize how the
143 [`EXPECT_PRED_FORMAT*`](reference/assertions.md#EXPECT_PRED_FORMAT) in the
156 [`EXPECT_PRED_FORMAT2`](reference/assertions.md#EXPECT_PRED_FORMAT), for
193 ### Windows HRESULT assertions
195 See [Windows HRESULT Assertions](reference/assertions.md#HRESULT) in the
[all …]
H A Dfaq.md202 particular, using it in GoogleTest comparison assertions (`EXPECT_EQ`, etc) will
283 the details at [Death Assertions](reference/assertions.md#death) in the
352 GoogleTest assertions in a destructor if your code could run on such a
357 See details for [`EXPECT_PRED*`](reference/assertions.md#EXPECT_PRED) in the
498 // Death assertions can be used anywhere in a function. In
/freebsd-14.2/tools/build/options/
H A DWITH_LLVM_ASSERTIONS1 Enable debugging assertions in LLVM.
H A DWITHOUT_LLVM_ASSERTIONS1 Disable debugging assertions in LLVM.
H A DWITHOUT_PTHREADS_ASSERTIONS1 Disable debugging assertions in pthreads library.
H A DWITH_MALLOC_PRODUCTION1 Disable assertions and statistics gathering in
H A DWITHOUT_MALLOC_PRODUCTION1 Enable assertions and statistics gathering in
/freebsd-14.2/contrib/googletest/
H A DREADME.md63 * Rich set of assertions: \
64 Googletest provides a variety of assertions, such as equality, inequality,
66 * User-defined assertions: \
67 You can define your own assertions with Googletest, making it simple to
/freebsd-14.2/sys/contrib/openzfs/config/
H A Duser-backtrace.m42 dnl backtrace(), for userspace assertions. glibc has this directly in libc.
H A Duser-libunwind.m410 [use libunwind for backtraces in userspace assertions]),
/freebsd-14.2/contrib/libcbor/test/
H A DCMakeLists.txt14 add_executable(${NAME} "${NAME}.c" assertions.c stream_expectations.c test_allocator.c)
/freebsd-14.2/contrib/unbound/doc/
H A DREADME.svn7 assertions, otherwise, use make clean; make after svn update.
/freebsd-14.2/contrib/googletest/docs/_data/
H A Dnavigation.yml29 url: "/reference/assertions.html"
/freebsd-14.2/contrib/bsnmp/tests/
H A Dcatch.hpp2808 Counts assertions; member
5490 Counts assertions; member
12596 assertions = m_totals.assertions; in sectionStarted()
12616 assertions.failed++; in testForMissingAssertions()
12621 Counts assertions = m_totals.assertions - endInfo.prevAssertions; in sectionEnded() local
12703 Counts assertions; in handleFatalErrorCondition() local
12704 assertions.failed = 1; in handleFatalErrorCondition()
12777 Counts assertions = m_totals.assertions - prevAssertions; in runCurrentTest()
14983 diff.assertions = assertions - other.assertions; in operator -()
14989 assertions += other.assertions; in operator +=()
[all …]
/freebsd-14.2/contrib/libfido2/
H A DNEWS3 ** winhello: support U2F AppID extension for assertions.
4 ** winhello: fix restrictive parsing of the hmac-secret on assertions.
/freebsd-14.2/contrib/ntp/libntp/
H A DMakefile.am11 lib/isc/include/isc/assertions.h \
94 lib/isc/assertions.c \
H A DMakefile.in183 ymd2yd.c lib/isc/assertions.c lib/isc/buffer.c \
206 am__objects_4 = lib/isc/assertions.$(OBJEXT) lib/isc/buffer.$(OBJEXT) \
269 ymd2yd.c lib/isc/assertions.c lib/isc/buffer.c \
337 ./$(DEPDIR)/ymd2yd.Po lib/isc/$(DEPDIR)/assertions.Po \
691 lib/isc/include/isc/assertions.h \
757 libisc_SRCS = lib/isc/assertions.c lib/isc/buffer.c \
929 lib/isc/assertions.$(OBJEXT): lib/isc/$(am__dirstamp) \
1121 @AMDEP_TRUE@@am__include@ @am__quote@lib/isc/$(DEPDIR)/assertions.Po@am__quote@ # am--include-marker
1407 -rm -f lib/isc/$(DEPDIR)/assertions.Po
1561 -rm -f lib/isc/$(DEPDIR)/assertions.Po
/freebsd-14.2/usr.sbin/ntp/libntp/
H A DMakefile54 ISC_SRCS= assertions.c \
/freebsd-14.2/share/doc/papers/
H A Dbsdreferences.bib5 …mputer Systems/Anderson et al. - 2014 - TESLA temporally enhanced system logic assertions.pdf:pdf},
9 title = {{TESLA: temporally enhanced system logic assertions}},
/freebsd-14.2/contrib/nvi/regex/
H A DWHATSNEW71 problem with assertions not being suppressed in the absence of REDEBUG.

123