| /freebsd/contrib/googletest/docs/reference/ |
| H A D | assertions.md | 1 # Assertions Reference
25 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
[all …]
|
| H A D | testing.md | 28 [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
368 [Adding Traces to Assertions](../advanced.md#adding-traces-to-assertions).
385 Similar to assertions, `GTEST_SKIP` allows streaming a custom message into it.
1430 See [Type Assertions](../advanced.md#type-assertions) for more information.
|
| /freebsd/share/man/man9/ |
| H A D | KASSERT.9 | 46 Assertions are widely used within the
51 Assertions are optional code; for non-recoverable error conditions an explicit
82 This eliminates the runtime overhead of widespread assertions from release
85 added as assertions without concern about their performance impact.
99 When adding new assertions, keep in mind their primary purpose: to aid in
109 Therefore, assertions should adhere to the following guidelines:
115 Unrelated conditions must appear in separate assertions.
118 into separate assertions.
|
| H A D | mutex.9 | 365 function allows assertions specified in
369 If the assertions are not true and the kernel is compiled with
374 Currently the following assertions are supported:
528 There are numerous assertions which will fail if this is attempted.
|
| H A D | rwlock.9 | 256 This function allows assertions specified in
260 If the assertions are not true and the kernel is compiled
266 Currently the following base assertions are supported:
|
| H A D | sx.9 | 216 for the assertions specified in
219 One of the following assertions must be specified:
242 In addition, one of the following optional assertions may be included with
|
| H A D | lock.9 | 343 for the assertions specified in
346 One of the following assertions must be specified:
366 In addition, one of the following optional assertions can be used with
|
| /freebsd/contrib/googletest/docs/ |
| H A D | primer.md | 81 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
99 ## Assertions section in GoogleTest Primer
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
[all …]
|
| H A D | advanced.md | 7 will show you more assertions as well as how to construct complex failure
11 ## More Assertions
14 assertions.
18 See [Explicit Success and Failure](reference/assertions.md#success-failure) in
19 the Assertions Reference.
21 ### Exception Assertions argument
23 See [Exception Assertions](reference/assertions.md#exceptions) in the Assertions
26 ### Predicate Assertions for Better Error Messages argument
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
[all …]
|
| H A D | quickstart-cmake.md | 88 // 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 D | quickstart-bazel.md | 77 // 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 D | faq.md | 181 particular, using it in GoogleTest comparison assertions (`EXPECT_EQ`, etc.)
262 the details at [Death Assertions](reference/assertions.md#death) in the
263 Assertions Reference.
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
337 Assertions Reference.
477 // Death assertions can be used anywhere in a function. In
|
| /freebsd/contrib/libcbor/test/ |
| H A D | stream_expectations.h | 4 #include "assertions.h"
77 /* Test harness -- calls `cbor_stream_decode` and checks assertions */
80 /* Verify all assertions were applied and clean up */
83 /* Assertions builders */
118 /* Assertions verifying callbacks */
|
| /freebsd/contrib/googletest/googletest/include/gtest/ |
| H A D | gtest-assertion-result.h | 62 // 1. Defining predicate functions to be used with Boolean test assertions
65 // used with predicate assertions (ASSERT_PRED_FORMAT*, etc).
92 // messages in EXPECT_FALSE and ASSERT_FALSE (negative assertions show up
109 // NB: Predicates that support negative Boolean assertions have reduced
111 // that have lots (tens of thousands) of positive Boolean assertions.
113 // To use this class with EXPECT_PRED_FORMAT assertions such as:
179 // Returns the text streamed into this AssertionResult. Test assertions
219 // with test assertions.
|
| /freebsd/contrib/googletest/ |
| H A D | README.md | 59 * Rich set of assertions: \
60 Googletest provides a variety of assertions, such as equality, inequality,
62 * User-defined assertions: \
63 You can define your own assertions with Googletest, making it simple to
|
| /freebsd/contrib/googletest/googletest/test/ |
| H A D | gtest_stress_test.cc | 30 // Tests that SCOPED_TRACE() and various Google Test assertions can be
79 // Calls a large number of Google Test assertions, where exactly one of them
89 // A bunch of assertions that should succeed. in ManyAsserts()
103 // is for testing whether Google Test can handle failed assertions in a in ManyAsserts()
117 // Tests using SCOPED_TRACE() and Google Test assertions in many threads
|
| /freebsd/contrib/googletest/docs/_data/ |
| H A D | navigation.yml | 28 - title: "Assertions"
29 url: "/reference/assertions.html"
|
| /freebsd/contrib/llvm-project/llvm/lib/Support/ |
| H A D | regutils.h | 45 /* switch off assertions (if not already off) if no REDEBUG */
48 #define NDEBUG /* no assertions please */
|
| /freebsd/lib/libc/regex/ |
| H A D | utils.h | 44 /* switch off assertions (if not already off) if no REDEBUG */
47 #define NDEBUG /* no assertions please */
|
| /freebsd/contrib/sendmail/libsm/ |
| H A D | assert.html | 100 <h2> Assertions </h2>
103 supports a style of programming in which assertions are used
143 each of the three kinds of assertions, for performance reasons.
159 to disable all assertions except for SM_REQUIRE, you can use
169 <h2> How To Write Complex or Expensive Assertions </h2>
|
| /freebsd/contrib/nvi/regex/ |
| H A D | utils.h | 44 /* switch off assertions (if not already off) if no REDEBUG */
47 #define NDEBUG /* no assertions please */
|
| /freebsd/contrib/ntp/libntp/lib/isc/include/isc/ |
| H A D | assertions.h | 19 * $Id: assertions.h,v 1.28 2009/09/29 23:48:04 tbox Exp $
21 /*! \file isc/assertions.h
|
| /freebsd/contrib/ntp/libntp/lib/isc/ |
| H A D | assertions.c | 18 /* $Id: assertions.c,v 1.26 2009/09/29 15:06:07 fdupont Exp $ */
27 #include <isc/assertions.h>
|
| /freebsd/crypto/libecc/ |
| H A D | meson.options | 9 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/libfido2/src/fido/ |
| H A D | types.h | 222 fido_assert_stmt *stmt; /* array of expected assertions */
223 size_t stmt_cnt; /* number of allocated assertions */
224 size_t stmt_len; /* number of received assertions */
|