Home
last modified time | relevance | path

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

123

/freebsd/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
159 See also the [Floating-Point Comparison](#floating-point) assertions to compare
222 The following assertions compare two **C strings**. To compare two `string`
225 These assertions also accept wide C strings (`wchar_t*`). If a comparison of two
263 The following assertions compare two floating-point values.
[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
465 [Adding Traces to Assertions](../advanced.md#adding-traces-to-assertions).
482 Similar to assertions, `GTEST_SKIP` allows streaming a custom message into it.
1527 See [Type Assertions](../advanced.md#type-assertions) for more information.
/freebsd/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
101 GoogleTest assertions are macros that resemble function calls. You test a class
102 or function by making assertions about its behavior. When an assertion fails,
107 The assertions come in pairs that test the same thing but have different effects
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
143 provided by GoogleTest, see the [Assertions Reference](reference/assertions.md).
[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.md67 // Demonstrate some basic assertions.
76 GoogleTest provides [assertions](primer.md#assertions) that you use to test the
78 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
23 See [Exception Assertions](reference/assertions.md#exceptions) in the Assertions
28 Even though GoogleTest has a rich set of assertions, they can never be complete,
45 [`EXPECT_PRED*`](reference/assertions.md#EXPECT_PRED) in the Assertions
76 To provide more readable messages in Boolean assertions (e.g. `EXPECT_TRUE()`),
114 (one third of Boolean assertions in the Google code base are negative ones), and
138 [`EXPECT_PRED*`](reference/assertions.md#EXPECT_PRED) and
139 [`EXPECT_TRUE`](reference/assertions.md#EXPECT_TRUE) unsatisfactory, or some
[all …]
H A Dfaq.md181 particular, using it in GoogleTest comparison assertions (`EXPECT_EQ`, etc.)
262 the details at [Death Assertions](reference/assertions.md#death) in the
331 GoogleTest assertions in a destructor if your code could run on such a
336 See details for [`EXPECT_PRED*`](reference/assertions.md#EXPECT_PRED) in the
477 // Death assertions can be used anywhere in a function. In
/freebsd/contrib/googletest/
H A DREADME.md50 * Rich set of assertions: \
51 Googletest provides a variety of assertions, such as equality, inequality,
53 * User-defined assertions: \
54 You can define your own assertions with Googletest, making it simple to
/freebsd/tools/build/options/
H A DWITHOUT_LLVM_ASSERTIONS1 Disable debugging assertions in LLVM.
H A DWITH_LLVM_ASSERTIONS1 Enable debugging assertions in LLVM.
H A DWITHOUT_PTHREADS_ASSERTIONS1 Disable debugging assertions in pthreads library.
H A DWITH_PTHREADS_ASSERTIONS1 Enable 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/crypto/libecc/
H A Dmeson.options9 option('with_debug', type: 'boolean', value : false, description: 'activate libecc debug assertions…
11 …ion('assert_print', type: 'boolean', value : false, description: 'activate printing on assertions')
/freebsd/contrib/libcbor/test/
H A DCMakeLists.txt14 add_executable(${NAME} "${NAME}.c" assertions.c stream_expectations.c test_allocator.c)
/freebsd/contrib/unbound/doc/
H A DREADME.svn7 assertions, otherwise, use make clean; make after svn update.
/freebsd/contrib/bsnmp/tests/
H A Dcatch.hpp2421 Counts& assertions ) = 0;
2808 Counts assertions; member
5490 Counts assertions; member
5765 Assertions assertions; member
5846 sectionNode.assertions.push_back(assertionStats); in assertionEnded()
8020 bool sectionStarted( SectionInfo const& sectionInfo, Counts& assertions ) override;
8061 bool testForMissingAssertions( Counts& assertions );
10946 assertions( _assertions ), in SectionStats()
12530 deltaTotals.assertions.failed++; in runTest()
12557 m_totals.assertions.passed++; in assertionEnded()
[all …]
/freebsd/sys/contrib/openzfs/config/
H A Duser-libunwind.m410 [use libunwind for backtraces in userspace assertions]),
/freebsd/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
[all...]
/freebsd/usr.sbin/ntp/libntp/
H A DMakefile54 ISC_SRCS= assertions.c \
/freebsd/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/contrib/llvm-project/libcxx/include/
H A D__config72 // mode and enables all checks available in the library, including internal assertions. Checks that are part of the
75 // Inside the library, assertions are categorized so they can be cherry-picked based on the chosen hardening mode. These
111 // a string view where only a subset of elements is possible to access). This category is for assertions violating
122 // - `_LIBCPP_ASSERT_INTERNAL` -- checks that internal invariants of the library hold. These assertions don't depend on
125 // - `_LIBCPP_ASSERT_UNCATEGORIZED` -- for assertions that haven't been properly classified yet.
/freebsd/contrib/nvi/regex/
H A DWHATSNEW71 problem with assertions not being suppressed in the absence of REDEBUG.

123