| /third_party/grpc/third_party/upb/third_party/lunit/ |
| D | lunit.lua | 193 stats.assertions = stats.assertions + 1
200 stats.assertions = stats.assertions + 1
210 stats.assertions = stats.assertions + 1
220 stats.assertions = stats.assertions + 1
230 stats.assertions = stats.assertions + 1
240 stats.assertions = stats.assertions + 1
250 stats.assertions = stats.assertions + 1
266 stats.assertions = stats.assertions + 1
282 stats.assertions = stats.assertions + 1
298 stats.assertions = stats.assertions + 1
[all …]
|
| /third_party/boost/libs/test/test/baseline-outputs/ |
| D | log-count-skipped-tests.pattern | 16 <testcase assertions="1" name="test_1" time="0.1234">
24 <testcase assertions="0" name="test_2" time="0.1234">
30 <testcase assertions="0" name="test_3" time="0.1234">
40 <testcase assertions="1" name="test_1" time="0.1234">
42 <testcase assertions="0" name="test_2" time="0.1234">
48 <testcase assertions="0" name="test_3" time="0.1234">
72 <testcase assertions="1" name="test_1" time="0.1234">
80 <testcase assertions="1" name="test_2" time="0.1234">
93 <testcase assertions="0" name="test_3" time="0.1234">
103 <testcase assertions="1" name="test_1" time="0.1234">
[all …]
|
| D | messages-in-datasets-test.pattern | 11 Test case fake_datatest_case/_0 did not check any assertions
20 Test case fake_datatest_case/_1 did not check any assertions
25 …assertions]]></Message><TestingTime>ZZZ</TestingTime></TestCase><TestCase name="_1" file="xxx/mess…
29 <testcase assertions="0" name="_0" time="0.1234">
49 - message: Test case fake_datatest_case/_0 did not check any assertions
53 <testcase assertions="0" name="_1" time="0.1234">
73 - message: Test case fake_datatest_case/_1 did not check any assertions
81 <testcase assertions="0" name="_0" time="0.1234">
83 <testcase assertions="0" name="_1" time="0.1234">
|
| D | log-formatter-test.pattern.junit | 10 <testcase assertions="0" name="almost_good_foo" time="0.1234">
19 - message: Test case 1 test cases inside/almost_good_foo did not check any assertions
33 <testcase assertions="0" name="good_foo" time="0.1234">
37 - message: Test case Timeout/good_foo did not check any assertions
41 <testcase assertions="1" name="timeout_foo" time="0.1234">
60 <testcase assertions="4" name="bad_foo" time="0.1234">
95 <testcase assertions="1" name="very_bad_foo" time="0.1234">
111 <testcase assertions="0" name="good_foo" time="0.1234">
115 - message: Test case 1 junit failure is not error/good_foo did not check any assertions
119 <testcase assertions="4" name="bad_foo2" time="0.1234">
|
| D | log-formatter-test.pattern | 5 Test case Fake Test Suite Hierarchy/1 test cases inside/good_foo did not check any assertions
10 …ke Test Suite Hierarchy/1 test cases inside/good_foo did not check any assertions]]></Message><Tes…
14 <testcase assertions="0" name="good_foo" time="0.1234">
18 …sage: Test case Fake Test Suite Hierarchy/1 test cases inside/good_foo did not check any assertions
26 <testcase assertions="0" name="good_foo" time="0.1234">
49 <testcase assertions="4" name="bad_foo" time="0.1234">
93 <testcase assertions="4" name="bad_foo" time="0.1234">
128 Test case 1 almost good test case inside/almost_good_foo did not check any assertions
133 … case 1 almost good test case inside/almost_good_foo did not check any assertions]]></Message><Tes…
137 <testcase assertions="0" name="almost_good_foo" time="0.1234">
[all …]
|
| D | global-fixtures-test.pattern | 35 Test case Fake Test Suite Hierarchy/1 test cases inside/good_foo did not check any assertions
54 …ke Test Suite Hierarchy/1 test cases inside/good_foo did not check any assertions]]></Message><Tes…
58 <testcase assertions="4" name="bad_foo" time="0.1234">
98 <testcase assertions="1" name="very_bad_foo" time="0.1234">
114 <testcase assertions="2" name="very_bad_exception" time="0.1234">
149 <testcase assertions="0" classname="1_test_cases_inside" name="good_foo" time="0.1234">
153 …sage: Test case Fake Test Suite Hierarchy/1 test cases inside/good_foo did not check any assertions
157 <testcase assertions="4" classname="1_bad_test_case_inside" name="bad_foo" time="0.1234">
201 <testcase assertions="4" name="bad_foo" time="0.1234">
230 <testcase assertions="1" name="very_bad_foo" time="0.1234">
[all …]
|
| /third_party/typescript/tests/baselines/reference/ |
| D | definiteAssignmentAssertions.errors.txt | 2 …0,6): error TS1263: Declarations with initializers cannot also have definite assignment assertions.
3 …1,6): error TS1263: Declarations with initializers cannot also have definite assignment assertions.
6 …sertions.ts(23,6): error TS1264: Declarations with definite assignment assertions must also have t…
9 …ertions.ts(69,10): error TS1264: Declarations with definite assignment assertions must also have t…
10 …,10): error TS1263: Declarations with initializers cannot also have definite assignment assertions.
11 …,10): error TS1263: Declarations with initializers cannot also have definite assignment assertions.
41 !!! error TS1263: Declarations with initializers cannot also have definite assignment assertions.
44 !!! error TS1263: Declarations with initializers cannot also have definite assignment assertions.
52 !!! error TS1264: Declarations with definite assignment assertions must also have type annotations.
104 !!! error TS1264: Declarations with definite assignment assertions must also have type annotations.
[all …]
|
| D | constantEnumAssert.errors.txt | 1 tests/cases/compiler/constantEnumAssert.ts(45,20): error TS1355: A 'const' assertions can only be a…
2 tests/cases/compiler/constantEnumAssert.ts(49,20): error TS1355: A 'const' assertions can only be a…
52 !!! error TS1355: A 'const' assertions can only be applied to references to enum members, or string…
58 !!! error TS1355: A 'const' assertions can only be applied to references to enum members, or string…
|
| D | jsFileCompilationNonNullAssertion.errors.txt | 1 /src/a.js(1,1): error TS8013: Non-null assertions can only be used in TypeScript files.
7 !!! error TS8013: Non-null assertions can only be used in TypeScript files.
|
| D | definiteAssignmentWithErrorStillStripped.errors.txt | 1 …lStripped.ts(2,6): error TS1264: Declarations with definite assignment assertions must also have t…
8 !!! error TS1264: Declarations with definite assignment assertions must also have type annotations.
|
| D | constAssertions.errors.txt | 2 …ions/typeAssertions/constAssertions.ts(61,10): error TS1355: A 'const' assertions can only be appl…
3 …ions/typeAssertions/constAssertions.ts(62,10): error TS1355: A 'const' assertions can only be appl…
4 …ions/typeAssertions/constAssertions.ts(63,10): error TS1355: A 'const' assertions can only be appl…
72 !!! error TS1355: A 'const' assertions can only be applied to references to enum members, or string…
75 !!! error TS1355: A 'const' assertions can only be applied to references to enum members, or string…
78 !!! error TS1355: A 'const' assertions can only be applied to references to enum members, or string…
|
| /third_party/typescript_eslint/packages/eslint-plugin/docs/rules/ |
| D | consistent-type-assertions.md | 1 # Enforces consistent usage of type assertions (`consistent-type-assertions`)
7 …assertions are also commonly referred as "type casting" in TypeScript (even though it is technical…
9 In addition to ensuring that type assertions are written in a consistent way, this rule also helps …
11 …const` assertions, [introduced in TypeScript 3.4](https://www.typescriptlang.org/docs/handbook/rel…
37 - `never` will enforce that you do not do any type assertions.
41 Some codebases like to go for an extra level of type safety, and ban assertions altogether via the …
89 If you do not want to enforce consistent type assertions.
|
| /third_party/musl/porting/liteos_m_iccarm/kernel/src/regex/ |
| D | regexec.c | 64 #define CHECK_ASSERTIONS(assertions) \ argument
65 (((assertions & ASSERT_AT_BOL) \
68 || ((assertions & ASSERT_AT_EOL) \
71 || ((assertions & ASSERT_AT_BOW) \
73 || ((assertions & ASSERT_AT_EOW) \
75 || ((assertions & ASSERT_AT_WB) \
78 || ((assertions & ASSERT_AT_WB_NEG) \
83 (((trans_i->assertions & ASSERT_CHAR_CLASS) \
86 || ((trans_i->assertions & ASSERT_CHAR_CLASS) \
90 || ((trans_i->assertions & ASSERT_CHAR_CLASS_NEG) \
[all …]
|
| /third_party/musl/porting/uniproton/kernel/src/regex/ |
| D | regexec.c | 64 #define CHECK_ASSERTIONS(assertions) \ argument
65 (((assertions & ASSERT_AT_BOL) \
68 || ((assertions & ASSERT_AT_EOL) \
71 || ((assertions & ASSERT_AT_BOW) \
73 || ((assertions & ASSERT_AT_EOW) \
75 || ((assertions & ASSERT_AT_WB) \
78 || ((assertions & ASSERT_AT_WB_NEG) \
83 (((trans_i->assertions & ASSERT_CHAR_CLASS) \
86 || ((trans_i->assertions & ASSERT_CHAR_CLASS) \
90 || ((trans_i->assertions & ASSERT_CHAR_CLASS_NEG) \
[all …]
|
| /third_party/musl/src/regex/ |
| D | regexec.c | 64 #define CHECK_ASSERTIONS(assertions) \ argument
65 (((assertions & ASSERT_AT_BOL) \
68 || ((assertions & ASSERT_AT_EOL) \
71 || ((assertions & ASSERT_AT_BOW) \
73 || ((assertions & ASSERT_AT_EOW) \
75 || ((assertions & ASSERT_AT_WB) \
78 || ((assertions & ASSERT_AT_WB_NEG) \
83 (((trans_i->assertions & ASSERT_CHAR_CLASS) \
86 || ((trans_i->assertions & ASSERT_CHAR_CLASS) \
90 || ((trans_i->assertions & ASSERT_CHAR_CLASS_NEG) \
[all …]
|
| /third_party/musl/porting/liteos_m/kernel/src/regex/ |
| D | regexec.c | 64 #define CHECK_ASSERTIONS(assertions) \ argument
65 (((assertions & ASSERT_AT_BOL) \
68 || ((assertions & ASSERT_AT_EOL) \
71 || ((assertions & ASSERT_AT_BOW) \
73 || ((assertions & ASSERT_AT_EOW) \
75 || ((assertions & ASSERT_AT_WB) \
78 || ((assertions & ASSERT_AT_WB_NEG) \
83 (((trans_i->assertions & ASSERT_CHAR_CLASS) \
86 || ((trans_i->assertions & ASSERT_CHAR_CLASS) \
90 || ((trans_i->assertions & ASSERT_CHAR_CLASS_NEG) \
[all …]
|
| /third_party/ltp/testcases/open_posix_testsuite/conformance/definitions/signal_h/ |
| D | coverage.txt | 1 This document explains why certain assertions were not tested.
5 6 through 12 - Did not test RTS assertions.
10 The assertions:
|
| /third_party/unity/docs/ |
| D | UnityAssertionsReference.md | 9 - Unity is mainly a rich collection of assertions and the support to gather up
10 and easily execute those assertions.
11 - The structure of Unity allows you to easily separate test assertions from
13 - Unity's assertions:
22 One way to think of Unity is simply as a rich collection of assertions you can
24 Unity provides a framework to easily organize and execute those assertions in
30 At their core, assertions are an establishment of truth - boolean truth. Was this
55 That's what Unity's collection of assertions do - capture context to give you
56 helpful, meaningful assertion failure messages. In fact, the assertions
81 marked as an optional parameter because some assertions only need a single
[all …]
|
| /third_party/node/test/parallel/ |
| D | test-dns-channel-cancel-promise.js | 43 const assertions = []; variable
49 assertions.push(
61 await Promise.all(assertions);
|
| /third_party/cJSON/tests/unity/docs/ |
| D | UnityAssertionsReference.md | 9 - Unity is mainly a rich collection of assertions and the support to gather up
10 and easily execute those assertions.
11 - The structure of Unity allows you to easily separate test assertions from
13 - Unity's assertions:
22 One way to think of Unity is simply as a rich collection of assertions you can
24 Unity provides a framework to easily organize and execute those assertions in
30 At their core, assertions are an establishment of truth - boolean truth. Was this
55 That's what Unity's collection of assertions do - capture context to give you
56 helpful, meaningful assertion failure messages. In fact, the assertions
79 marked as an optional parameter because some assertions only need a single
[all …]
|
| /third_party/boost/libs/test/doc/testing_tools/ |
| D | boost_test_debugging.qbk | 9 [section:debugging Debugging the assertions]
18 building of expression trees inside assertions.
26 of sequence comparisons. This may turn passing assertions into failing assertions and vice-versa.
31 The __UTF__ gives you another option to compile two versions of the assertions and select the one t…
|
| D | expected_failures.qbk | 10 While in a perfect world all test assertions should pass in order for a test module to pass, in som…
16 This feature allows specifying an expected number of failed assertions per test unit. The value is …
42 The decorator __decorator_expected_failures__ defines the number of assertions that are expected to…
43 unit. It is reported as failure when the number of failed assertions is greater than the declared e…
44 failures. If the number of failed assertions is less than the number of expected failures a message…
50 In the above example, we first run all test cases with four failed assertions. The total number of …
|
| /third_party/ltp/testcases/open_posix_testsuite/conformance/interfaces/pthread_kill/ |
| D | coverage.txt | 7 4 IMPLICITLY tested by assertions 6 and 7.
8 5 IMPLICITLY tested by assertions 6 and 7.
|
| /third_party/boost/libs/test/doc/test_organization/ |
| D | decorators.qbk | 80 // assertions
86 // assertions
93 // assertions
99 // assertions
139 // assertions
149 // assertions
159 // assertions
|
| /third_party/boost/libs/config/test/ |
| D | boost_has_static_assert.ipp | 9 // TITLE: static assertions
10 // DESCRIPTION: The compiler supports C++0x static assertions
|