Home
last modified time | relevance | path

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

1234

/freebsd-12.1/contrib/googletest/googletest/docs/
H A Dprimer.md82 When using googletest, you start by writing *assertions*, which are statements
87 *Tests* use assertions to verify the tested code's behavior. If a test crashes
102 googletest assertions are macros that resemble function calls. You test a class
103 or function by making assertions about its behavior. When an assertion fails,
139 These assertions do basic true/false condition testing.
155 This section describes assertions that compare two values.
174 These assertions can work with a user-defined type, but only if you define the
219 The assertions in this group compare two **C strings**. If you want to compare
249 use the various googletest assertions to check values.
565 _unsafe_ to use Google Test assertions from two threads concurrently on
[all …]
H A Dadvanced.md8 show you more assertions as well as how to construct complex failure messages,
15 assertions.
19 These three assertions do not actually test a value or expression. Instead, they
28 considered successful only if none of its assertions fail during its execution.
351 The following assertions allow you to choose the acceptable error bound:
455 ### Windows HRESULT assertions
457 These assertions test for `HRESULT` success or failure.
543 assertions in them. You'll get a compilation error if you try. A simple
550 partially-destructed state. Use assertions carefully in these situations!
652 code, see [Exception Assertions](#exception-assertions).
[all …]
H A Dfaq.md219 particular, using it in googletest comparison assertions (`EXPECT_EQ`, etc) will
347 googletest assertions in a destructor if your code could run on such a
572 // Death assertions can be used any where in a function. In
/freebsd-12.1/contrib/googletest/googletest/
H A DCHANGES40 * Failures from ad hoc test assertions run before RUN_ALL_TESTS() are
62 * New feature: assertions can be safely called in multiple threads
104 * New feature: ability to use Google Test assertions in other testing
142 * New feature: exception assertions.
/freebsd-12.1/contrib/ntp/libntp/
H A DMakefile.in164 ymd2yd.c $(srcdir)/../lib/isc/assertions.c \
192 am__objects_3 = assertions.$(OBJEXT) buffer.$(OBJEXT) \
250 ymd2yd.c $(srcdir)/../lib/isc/assertions.c \
618 libisc_SRCS = $(srcdir)/../lib/isc/assertions.c \
787 @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/assertions.Po@am__quote@
913 assertions.o: $(srcdir)/../lib/isc/assertions.c
914 …assertions.o -MD -MP -MF $(DEPDIR)/assertions.Tpo -c -o assertions.o `test -f '$(srcdir)/../lib/is…
915 @am__fastdepCC_TRUE@ $(AM_V_at)$(am__mv) $(DEPDIR)/assertions.Tpo $(DEPDIR)/assertions.Po
920 assertions.obj: $(srcdir)/../lib/isc/assertions.c
921 …S) $(CPPFLAGS) $(AM_CFLAGS) $(CFLAGS) -MT assertions.obj -MD -MP -MF $(DEPDIR)/assertions.Tpo -c -…
[all …]
H A DMakefile.am8 $(srcdir)/../lib/isc/assertions.c \
/freebsd-12.1/contrib/unbound/doc/
H A DREADME.svn7 assertions, otherwise, use make clean; make after svn update.
H A DREADME34 This enables assertions in the code that guard against a variety of
/freebsd-12.1/contrib/ntp/lib/isc/win32/
H A Dlibisc.mak118 -@erase "$(INTDIR)\assertions.obj"
240 "$(INTDIR)\assertions.obj" \
312 -@erase "$(INTDIR)\assertions.obj"
313 -@erase "$(INTDIR)\assertions.sbr"
509 "$(INTDIR)\assertions.sbr" \
597 "$(INTDIR)\assertions.obj" \
1099 SOURCE=..\assertions.c
1104 "$(INTDIR)\assertions.obj" : $(SOURCE) "$(INTDIR)"
1111 "$(INTDIR)\assertions.obj" "$(INTDIR)\assertions.sbr" : $(SOURCE) "$(INTDIR)"
H A Dlibisc.dsp206 SOURCE=..\include\isc\assertions.h
586 SOURCE=..\assertions.c
/freebsd-12.1/contrib/googletest/
H A DREADME.md37 * A rich set of assertions.
38 * User-defined assertions.
/freebsd-12.1/usr.sbin/ntp/libntp/
H A DMakefile54 ISC_SRCS= assertions.c \
/freebsd-12.1/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-12.1/contrib/binutils/gas/
H A DCONTRIBUTORS30 ports, updated "know" assertions and made them work, much other
/freebsd-12.1/contrib/ncurses/
H A DREADME.MinGW96 --enable-assertions \
H A Dconfigure.in1282 ### use option --enable-assertions to turn on generation of assertion code
1283 AC_MSG_CHECKING(if you want to enable runtime assertions)
1284 AC_ARG_ENABLE(assertions, optenable
1285 [ --enable-assertions test: turn on generation of assertion code],
/freebsd-12.1/lib/libc/regex/
H A DWHATSNEW71 problem with assertions not being suppressed in the absence of REDEBUG.
/freebsd-12.1/contrib/nvi/regex/
H A DWHATSNEW71 problem with assertions not being suppressed in the absence of REDEBUG.
/freebsd-12.1/contrib/llvm/lib/Support/
H A Dregengine.inc369 (void)dp; /* avoid warning if assertions off */
409 (void)dp; /* avoid warning if assertions off */
447 (void)dp; /* avoid warning if assertions off */
/freebsd-12.1/contrib/libarchive/libarchive/test/
H A Dmain.c253 static int assertions = 0; variable
332 ++assertions; in assertion_count()
3176 printf(" Assertions checked:%8d\n", assertions); in main()
/freebsd-12.1/contrib/libarchive/test_utils/
H A Dtest_main.c381 static int assertions = 0; variable
460 ++assertions; in assertion_count()
4074 printf(" Assertions checked:%8d\n", assertions); in main()
/freebsd-12.1/contrib/googletest/googlemock/docs/
H A DCheatSheet.md80 …the mock objects; if necessary, check the result using [Google Test](../../googletest/) assertions.
352 …ssion, m)`|Generates a [fatal failure](../../googletest/docs/primer.md#assertions) if the value of…
/freebsd-12.1/contrib/gcc/
H A Dconfig.in36 /* Define if you want assertions enabled. This is a cheap check. */
99 /* Define if you want runtime assertions enabled. This is a cheap check. */
/freebsd-12.1/contrib/bzip2/
H A DCHANGES310 * Tighten up a couple of assertions in blocksort.c following automated
/freebsd-12.1/contrib/jemalloc/
H A DChangeLog403 - Remove overly restrictive assertions related to the cactive statistic. This
1174 - Fix assertions in arena_purge() (for real this time).
1299 - Remove bad assertions in fork handler functions. These assertions could

1234