| /freebsd-13.1/contrib/googletest/googletest/docs/ |
| H A D | samples.md | 16 * Sample #6 demonstrates type-parameterized tests. 17 * Sample #7 teaches the basics of value-parameterized tests. 18 * Sample #8 shows using `Combine()` in value-parameterized tests.
|
| H A D | faq.md | 93 … interface satisfy some common requirements. Should I use typed tests or value-parameterized tests? 96 value-parameterized tests can get it done. It's really up to you the user to 105 * Value-parameterized tests can be easier to write if you need different code 111 help you quickly identify which implementation is wrong. Value-parameterized 120 when using value-parameterized tests.
|
| H A D | advanced.md | 1323 *Value-parameterized tests* allow you to test your code with different 1337 To write value-parameterized tests, first you should define a fixture class. It 1369 as you want. The `_P` suffix is for "parameterized" or "pattern", whichever you 1458 Sometimes you may want to define value-parameterized tests in a library and let 1468 1. Put the definition of the parameterized test fixture class (e.g. `FooTest`) 1523 First, define a fixture class template. It should be parameterized by a type. 1580 *Type-parameterized tests* are like typed tests, except that they don't require 1586 type-parameterized tests to verify properties that any valid implementation of 1601 Next, declare that you will define a type-parameterized test case: 1607 Then, use `TYPED_TEST_P()` to define a type-parameterized test. You can repeat
|
| /freebsd-13.1/contrib/ncurses/ncurses/tinfo/ |
| H A D | captoinfo.c | 297 _nc_captoinfo(const char *cap, const char *s, int const parameterized) in _nc_captoinfo() argument 308 DEBUG_THIS(("_nc_captoinfo params %d, %s", parameterized, s)); in _nc_captoinfo() 316 if (parameterized >= 0 && isdigit(UChar(*s))) in _nc_captoinfo() 325 if (parameterized < 1) { in _nc_captoinfo() 616 _nc_infotocap(const char *cap GCC_UNUSED, const char *str, int const parameterized) in _nc_infotocap() argument 634 DEBUG_THIS(("_nc_infotocap params %d, %s", parameterized, str)); in _nc_infotocap() 818 } else if (*str != '%' || (parameterized < 1)) { in _nc_infotocap()
|
| /freebsd-13.1/contrib/googletest/googletest/include/gtest/ |
| H A D | gtest-param-test.h.pump | 33 // Macros and functions for implementing parameterized tests 43 // Value-parameterized tests allow you to test your code with different 46 // Here is how you use value-parameterized tests: 50 // To write value-parameterized tests, first you should define a fixture 62 // Then, use the TEST_P macro to define as many parameterized tests 63 // for this fixture as you want. The _P suffix is for "parameterized" 153 // A parameterized test fixture must be derived from testing::Test and from 161 // You can inherit all the usual members for a non-parameterized test 170 // This is an ordinary non-parameterized test. 195 // parameterized tests. When a parameterized test case is instantiated
|
| /freebsd-13.1/contrib/googletest/googletest/ |
| H A D | CHANGES | 38 * Parameters of value-parameterized tests are now printed in the 49 * Value-parameterized test fixtures can now derive from Test and 127 * New feature: value-parameterized tests. 141 * New feature: type-parameterized tests.
|
| /freebsd-13.1/contrib/ncurses/ncurses/ |
| H A D | llib-ltictw | 72 int const parameterized) 79 int const parameterized)
|
| H A D | llib-lticw | 72 int const parameterized) 79 int const parameterized)
|
| H A D | llib-ltic | 72 int const parameterized) 79 int const parameterized)
|
| H A D | llib-ltict | 72 int const parameterized) 79 int const parameterized)
|
| H A D | llib-lncurses | 4218 int const parameterized) 4225 int const parameterized)
|
| H A D | llib-lncursest | 4339 int const parameterized) 4346 int const parameterized)
|
| H A D | llib-lncursestw | 5328 int const parameterized) 5335 int const parameterized)
|
| H A D | llib-lncursesw | 5207 int const parameterized) 5214 int const parameterized)
|
| /freebsd-13.1/contrib/googletest/ |
| H A D | README.md | 41 * Value-parameterized tests. 42 * Type-parameterized tests.
|
| /freebsd-13.1/contrib/googletest/googletest/include/gtest/internal/ |
| H A D | gtest-type-util.h.pump | 33 // Type utilities needed for implementing typed and type-parameterized 37 // type-parameterized tests in one type-parameterized test case.
|
| H A D | gtest-param-util-generated.h.pump | 34 // Type and function utilities for implementing parameterized tests.
|
| /freebsd-13.1/contrib/llvm-project/llvm/lib/Target/Mips/ |
| H A D | Relocation.txt | 49 template pattern parameterized over the load upper immediate
|
| /freebsd-13.1/contrib/googletest/googlemock/docs/ |
| H A D | DesignDoc.md | 155 You can view `ACTION` as a degenerated parameterized action where the 279 We will also add `MATCHER_P`, `MATCHER_P2`, and etc for parameterized
|
| H A D | CheatSheet.md | 432 | `ACTION_Pk(Foo, p1, ..., pk) { statements; }` | Defines a parameterized action `Foo(p1, ..., pk)`…
|
| /freebsd-13.1/contrib/ncurses/ |
| H A D | README | 191 for the code that hacks termcap parameterized strings into terminfo.
|
| /freebsd-13.1/contrib/llvm-project/llvm/lib/Target/Hexagon/ |
| H A D | HexagonPatternsHVX.td | 424 // The "source" types are not legal, and there are no parameterized
|
| /freebsd-13.1/contrib/llvm-project/llvm/include/llvm/Target/ |
| H A D | Target.td | 64 // The register size/alignment information, parameterized by a HW mode. 220 // The register size/alignment information, parameterized by a HW mode.
|
| /freebsd-13.1/contrib/llvm-project/llvm/lib/Target/RISCV/ |
| H A D | RISCVInstrInfo.td | 292 // A parameterized register class alternative to i32imm/i64imm from Target.td.
|
| /freebsd-13.1/contrib/flex/ |
| H A D | ONEWS | 1013 - Makefile has been further parameterized to aid in porting.
|