Searched full:foo* (Results 126 - 150 of 234) sorted by relevance

12345678910

/gem5/ext/googletest/googlemock/test/
H A Dgmock_output_test_golden.txt3 FILE:#: EXPECT_CALL(foo_, Bar2(0, _)) invoked
6 FILE:#: Mock function call matches EXPECT_CALL(foo_, Bar2(0, _))...
13 FILE:#: EXPECT_CALL(foo_, Bar3(0, _)) invoked
16 FILE:#: Mock function call matches EXPECT_CALL(foo_, Bar3(0, _))...
23 FILE:#: Too few actions specified in EXPECT_CALL(foo_, Bar2(_, _))...
26 FILE:#: Actions ran out in EXPECT_CALL(foo_, Bar2(_, _))...
38 FILE:#: EXPECT_CALL(foo_, Bar2(0, _))...
51 FILE:#: EXPECT_CALL(foo_, Bar3(0, _))...
95 FILE:#: tried expectation #0: EXPECT_CALL(foo_, Bar2(_, _))...
100 FILE:#: tried expectation #1: EXPECT_CALL(foo_, Bar
[all...]
H A Dgmock_stress_test.cc150 MockFoo foo; local
151 ON_CALL(foo, Bar(_))
153 ON_CALL(foo, Baz(_, _))
155 ON_CALL(foo, Baz(_, "you"))
158 EXPECT_CALL(foo, Bar(0))
160 EXPECT_CALL(foo, Baz(_, _));
161 EXPECT_CALL(foo, Baz("hi", "you"))
165 EXPECT_EQ(1, foo.Bar(0));
166 EXPECT_EQ(1, foo.Bar(0));
167 EXPECT_EQ('z', foo
200 MockFoo foo; local
230 Helper2(MockFoo* foo) argument
239 MockFoo foo; local
[all...]
H A Dgmock_test.cc79 "foo.exe",
84 "foo.exe",
93 "foo.exe",
99 "foo.exe",
108 "foo.exe",
114 "foo.exe",
124 "foo.exe",
131 "foo.exe",
153 L"foo.exe",
158 L"foo
[all...]
/gem5/ext/googletest/googletest/
H A DREADME.md230 FOO, you can add
235 from `FOO` to `GTEST_FOO`. Currently `FOO` can be `FAIL`, `SUCCEED`,
/gem5/ext/googletest/googletest/docs/
H A DAdvancedGuide.md65 ASSERT_THROW(Foo(5), bar_exception);
247 argument has type `Foo`, you can declare it as either `Foo` or `const Foo&`,
385 template <typename T> class Foo {
392 void Test1() { Foo<bool> foo; }
394 will _not_ generate a compiler error, as `Foo<bool>::Bar()` is never
397 void Test2() { Foo<bool> foo; fo
[all...]
H A DDevGuide.md90 source (`foo.h.pump`) and re-generate the C++ file using Pump. You
H A DFAQ.md25 * It's easy to write assertions that generate informative messages: you just use the stream syntax to append any additional information, e.g. `ASSERT_EQ(5, Foo(i)) << " where i = " << i;`. It doesn't require a new set of macros or special functions.
68 1. If `TestCaseName` ends with an `_` (say, `Foo_`), we get `Foo__TestName_Test`, which is invalid.
263 class FooTest : public ::testing::Test {};
265 TEST_F(FooTest, DoesThis) { ... }
269 typedef ::testing::Test FooTest;
271 TEST_F(FooTest, DoesThat) { ... }
297 if (FooCondition()) {
311 Foo(buffer, i)
339 // foo
[all...]
H A DPrimer.md304 `FooTest` where `Foo` is the class being tested.
405 #include "this/package/foo.h"
410 // The fixture for testing class Foo.
411 class FooTest : public ::testing::Test {
416 FooTest() {
420 virtual ~FooTest() {
437 // Objects declared here can be used by all tests in the test case for Foo.
440 // Tests that the Foo::Bar() method does Abc.
441 TEST_F(FooTest, MethodBarDoesAb
[all...]
H A DPumpManual.md31 programmer writes a `foo.pump` file which contains C++ code plus meta
56 // Foo$i does blah for $i-ary predicates.
59 class Foo$i {
75 // Foo0 does blah for 0-ary predicates.
77 class Foo0 {
81 // Foo1 does blah for 1-ary predicates.
83 class Foo1 {
87 // Foo2 does blah for 2-ary predicates.
89 class Foo2 {
93 // Foo3 doe
[all...]
H A DV1_5_AdvancedGuide.md63 ASSERT_THROW(Foo(5), bar_exception);
245 argument has type `Foo`, you can declare it as either `Foo` or `const Foo&`,
383 template <typename T> class Foo {
390 void Test1() { Foo<bool> foo; }
392 will _not_ generate a compiler error, as `Foo<bool>::Bar()` is never
395 void Test2() { Foo<bool> foo; fo
[all...]
H A DV1_5_FAQ.md25 * It's easy to write assertions that generate informative messages: you just use the stream syntax to append any additional information, e.g. `ASSERT_EQ(5, Foo(i)) << " where i = " << i;`. It doesn't require a new set of macros or special functions.
166 class FooTest : public ::testing::Test {};
168 TEST_F(FooTest, DoesThis) { ... }
172 typedef ::testing::Test FooTest;
174 TEST_F(FooTest, DoesThat) { ... }
200 if (FooCondition()) {
214 Foo(buffer, i)
242 // foo.h
243 class Foo {
249 You also need to define it _outside_ of the class body in `foo
[all...]
H A DV1_5_Primer.md299 `FooTest` where `Foo` is the class being tested.
400 #include "this/package/foo.h"
405 // The fixture for testing class Foo.
406 class FooTest : public ::testing::Test {
411 FooTest() {
415 virtual ~FooTest() {
432 // Objects declared here can be used by all tests in the test case for Foo.
435 // Tests that the Foo::Bar() method does Abc.
436 TEST_F(FooTest, MethodBarDoesAb
[all...]
H A DV1_5_PumpManual.md31 programmer writes a `foo.pump` file which contains C++ code plus meta
56 // Foo$i does blah for $i-ary predicates.
59 class Foo$i {
75 // Foo0 does blah for 0-ary predicates.
77 class Foo0 {
81 // Foo1 does blah for 1-ary predicates.
83 class Foo1 {
87 // Foo2 does blah for 2-ary predicates.
89 class Foo2 {
93 // Foo3 doe
[all...]
H A DV1_6_AdvancedGuide.md63 ASSERT_THROW(Foo(5), bar_exception);
245 argument has type `Foo`, you can declare it as either `Foo` or `const Foo&`,
383 template <typename T> class Foo {
390 void Test1() { Foo<bool> foo; }
392 will _not_ generate a compiler error, as `Foo<bool>::Bar()` is never
395 void Test2() { Foo<bool> foo; fo
[all...]
H A DV1_6_FAQ.md25 * It's easy to write assertions that generate informative messages: you just use the stream syntax to append any additional information, e.g. `ASSERT_EQ(5, Foo(i)) << " where i = " << i;`. It doesn't require a new set of macros or special functions.
68 1. If `TestCaseName` ends with an `_` (say, `Foo_`), we get `Foo__TestName_Test`, which is invalid.
263 class FooTest : public ::testing::Test {};
265 TEST_F(FooTest, DoesThis) { ... }
269 typedef ::testing::Test FooTest;
271 TEST_F(FooTest, DoesThat) { ... }
297 if (FooCondition()) {
311 Foo(buffer, i)
339 // foo
[all...]
H A DV1_6_Primer.md303 `FooTest` where `Foo` is the class being tested.
404 #include "this/package/foo.h"
409 // The fixture for testing class Foo.
410 class FooTest : public ::testing::Test {
415 FooTest() {
419 virtual ~FooTest() {
436 // Objects declared here can be used by all tests in the test case for Foo.
439 // Tests that the Foo::Bar() method does Abc.
440 TEST_F(FooTest, MethodBarDoesAb
[all...]
H A DV1_6_PumpManual.md31 programmer writes a `foo.pump` file which contains C++ code plus meta
56 // Foo$i does blah for $i-ary predicates.
59 class Foo$i {
75 // Foo0 does blah for 0-ary predicates.
77 class Foo0 {
81 // Foo1 does blah for 1-ary predicates.
83 class Foo1 {
87 // Foo2 does blah for 2-ary predicates.
89 class Foo2 {
93 // Foo3 doe
[all...]
H A DV1_7_AdvancedGuide.md63 ASSERT_THROW(Foo(5), bar_exception);
245 argument has type `Foo`, you can declare it as either `Foo` or `const Foo&`,
383 template <typename T> class Foo {
390 void Test1() { Foo<bool> foo; }
392 will _not_ generate a compiler error, as `Foo<bool>::Bar()` is never
395 void Test2() { Foo<bool> foo; fo
[all...]
H A DV1_7_FAQ.md25 * It's easy to write assertions that generate informative messages: you just use the stream syntax to append any additional information, e.g. `ASSERT_EQ(5, Foo(i)) << " where i = " << i;`. It doesn't require a new set of macros or special functions.
68 1. If `TestCaseName` ends with an `_` (say, `Foo_`), we get `Foo__TestName_Test`, which is invalid.
263 class FooTest : public ::testing::Test {};
265 TEST_F(FooTest, DoesThis) { ... }
269 typedef ::testing::Test FooTest;
271 TEST_F(FooTest, DoesThat) { ... }
297 if (FooCondition()) {
311 Foo(buffer, i)
339 // foo
[all...]
H A DV1_7_Primer.md303 `FooTest` where `Foo` is the class being tested.
404 #include "this/package/foo.h"
409 // The fixture for testing class Foo.
410 class FooTest : public ::testing::Test {
415 FooTest() {
419 virtual ~FooTest() {
436 // Objects declared here can be used by all tests in the test case for Foo.
439 // Tests that the Foo::Bar() method does Abc.
440 TEST_F(FooTest, MethodBarDoesAb
[all...]
H A DV1_7_PumpManual.md31 programmer writes a `foo.pump` file which contains C++ code plus meta
56 // Foo$i does blah for $i-ary predicates.
59 class Foo$i {
75 // Foo0 does blah for 0-ary predicates.
77 class Foo0 {
81 // Foo1 does blah for 1-ary predicates.
83 class Foo1 {
87 // Foo2 does blah for 2-ary predicates.
89 class Foo2 {
93 // Foo3 doe
[all...]
/gem5/ext/googletest/googletest/include/gtest/
H A Dgtest-death-test.h158 // path separator (e.g. path/to/foo_test and
159 // /absolute/path/to/bar_test are fine, but foo_test is not). This
H A Dgtest-message.h71 // testing::Message foo;
72 // foo << 1 << " != " << 2;
73 // std::cout << foo;
H A Dgtest-param-test.h60 class FooTest : public ::testing::TestWithParam<const char*> {
68 TEST_P(FooTest, DoesBlah) {
71 EXPECT_TRUE(foo.Blah(GetParam()));
75 TEST_P(FooTest, HasBlahBlah) {
100 // The following statement will instantiate tests from the FooTest test case
104 FooTest,
114 // * InstantiationName/FooTest.DoesBlah/0 for "meeny"
115 // * InstantiationName/FooTest.DoesBlah/1 for "miny"
116 // * InstantiationName/FooTest.DoesBlah/2 for "moe"
117 // * InstantiationName/FooTest
[all...]
H A Dgtest-param-test.h.pump59 class FooTest : public ::testing::TestWithParam<const char*> {
67 TEST_P(FooTest, DoesBlah) {
70 EXPECT_TRUE(foo.Blah(GetParam()));
74 TEST_P(FooTest, HasBlahBlah) {
99 // The following statement will instantiate tests from the FooTest test case
103 FooTest,
113 // * InstantiationName/FooTest.DoesBlah/0 for "meeny"
114 // * InstantiationName/FooTest.DoesBlah/1 for "miny"
115 // * InstantiationName/FooTest.DoesBlah/2 for "moe"
116 // * InstantiationName/FooTest
[all...]

Completed in 40 milliseconds

12345678910