2013-03-01 01:54:22 +00:00
|
|
|
// This file was GENERATED by command:
|
|
|
|
|
// pump.py gmock-generated-nice-strict.h.pump
|
|
|
|
|
// DO NOT EDIT BY HAND!!!
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
// Copyright 2008, Google Inc.
|
|
|
|
|
// All rights reserved.
|
|
|
|
|
//
|
|
|
|
|
// Redistribution and use in source and binary forms, with or without
|
|
|
|
|
// modification, are permitted provided that the following conditions are
|
|
|
|
|
// met:
|
|
|
|
|
//
|
|
|
|
|
// * Redistributions of source code must retain the above copyright
|
|
|
|
|
// notice, this list of conditions and the following disclaimer.
|
|
|
|
|
// * Redistributions in binary form must reproduce the above
|
|
|
|
|
// copyright notice, this list of conditions and the following disclaimer
|
|
|
|
|
// in the documentation and/or other materials provided with the
|
|
|
|
|
// distribution.
|
|
|
|
|
// * Neither the name of Google Inc. nor the names of its
|
|
|
|
|
// contributors may be used to endorse or promote products derived from
|
|
|
|
|
// this software without specific prior written permission.
|
|
|
|
|
//
|
|
|
|
|
// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
|
|
|
|
// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
|
|
|
|
// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
|
|
|
|
|
// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
|
|
|
|
// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
|
|
|
// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
|
|
|
|
|
// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
|
|
|
|
// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
|
|
|
|
// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
|
|
|
|
// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
|
|
|
|
// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
2018-08-14 18:04:07 +00:00
|
|
|
|
2008-12-10 05:08:54 +00:00
|
|
|
|
2013-03-01 01:54:22 +00:00
|
|
|
// Implements class templates NiceMock, NaggyMock, and StrictMock.
|
2008-12-10 05:08:54 +00:00
|
|
|
//
|
|
|
|
|
// Given a mock class MockFoo that is created using Google Mock,
|
|
|
|
|
// NiceMock<MockFoo> is a subclass of MockFoo that allows
|
|
|
|
|
// uninteresting calls (i.e. calls to mock methods that have no
|
2013-03-01 01:54:22 +00:00
|
|
|
// EXPECT_CALL specs), NaggyMock<MockFoo> is a subclass of MockFoo
|
|
|
|
|
// that prints a warning when an uninteresting call occurs, and
|
|
|
|
|
// StrictMock<MockFoo> is a subclass of MockFoo that treats all
|
|
|
|
|
// uninteresting calls as errors.
|
2008-12-10 05:08:54 +00:00
|
|
|
//
|
2013-03-01 01:54:22 +00:00
|
|
|
// Currently a mock is naggy by default, so MockFoo and
|
|
|
|
|
// NaggyMock<MockFoo> behave like the same. However, we will soon
|
|
|
|
|
// switch the default behavior of mocks to be nice, as that in general
|
|
|
|
|
// leads to more maintainable tests. When that happens, MockFoo will
|
|
|
|
|
// stop behaving like NaggyMock<MockFoo> and start behaving like
|
|
|
|
|
// NiceMock<MockFoo>.
|
2008-12-10 05:08:54 +00:00
|
|
|
//
|
2013-03-01 01:54:22 +00:00
|
|
|
// NiceMock, NaggyMock, and StrictMock "inherit" the constructors of
|
2018-04-05 20:09:17 +00:00
|
|
|
// their respective base class. Therefore you can write
|
|
|
|
|
// NiceMock<MockFoo>(5, "a") to construct a nice mock where MockFoo
|
|
|
|
|
// has a constructor that accepts (int, const char*), for example.
|
2013-03-01 01:54:22 +00:00
|
|
|
//
|
|
|
|
|
// A known limitation is that NiceMock<MockFoo>, NaggyMock<MockFoo>,
|
|
|
|
|
// and StrictMock<MockFoo> only works for mock methods defined using
|
|
|
|
|
// the MOCK_METHOD* family of macros DIRECTLY in the MockFoo class.
|
|
|
|
|
// If a mock method is defined in a base class of MockFoo, the "nice"
|
|
|
|
|
// or "strict" modifier may not affect it, depending on the compiler.
|
|
|
|
|
// In particular, nesting NiceMock, NaggyMock, and StrictMock is NOT
|
|
|
|
|
// supported.
|
2008-12-10 05:08:54 +00:00
|
|
|
|
2018-07-27 15:15:08 +00:00
|
|
|
// GOOGLETEST_CM0002 DO NOT DELETE
|
|
|
|
|
|
2008-12-10 05:08:54 +00:00
|
|
|
#ifndef GMOCK_INCLUDE_GMOCK_GMOCK_GENERATED_NICE_STRICT_H_
|
|
|
|
|
#define GMOCK_INCLUDE_GMOCK_GMOCK_GENERATED_NICE_STRICT_H_
|
|
|
|
|
|
2010-09-14 05:38:21 +00:00
|
|
|
#include "gmock/gmock-spec-builders.h"
|
|
|
|
|
#include "gmock/internal/gmock-port.h"
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
namespace testing {
|
|
|
|
|
|
|
|
|
|
template <class MockClass>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
class NiceMock : public MockClass {
|
2008-12-10 05:08:54 +00:00
|
|
|
public:
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
NiceMock() : MockClass() {
|
|
|
|
|
::testing::Mock::AllowUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2018-04-05 20:09:17 +00:00
|
|
|
|
|
|
|
|
#if GTEST_LANG_CXX11
|
2018-04-12 18:00:38 +00:00
|
|
|
// Ideally, we would inherit base class's constructors through a using
|
|
|
|
|
// declaration, which would preserve their visibility. However, many existing
|
|
|
|
|
// tests rely on the fact that current implementation reexports protected
|
|
|
|
|
// constructors as public. These tests would need to be cleaned up first.
|
|
|
|
|
|
2018-04-05 20:09:17 +00:00
|
|
|
// Single argument constructor is special-cased so that it can be
|
|
|
|
|
// made explicit.
|
|
|
|
|
template <typename A>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
explicit NiceMock(A&& arg) : MockClass(std::forward<A>(arg)) {
|
|
|
|
|
::testing::Mock::AllowUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2018-04-05 20:09:17 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename... An>
|
|
|
|
|
NiceMock(A1&& arg1, A2&& arg2, An&&... args)
|
|
|
|
|
: MockClass(std::forward<A1>(arg1), std::forward<A2>(arg2),
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
std::forward<An>(args)...) {
|
|
|
|
|
::testing::Mock::AllowUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2018-04-05 20:09:17 +00:00
|
|
|
#else
|
|
|
|
|
// C++98 doesn't have variadic templates, so we have to define one
|
|
|
|
|
// for each arity.
|
2008-12-10 05:08:54 +00:00
|
|
|
template <typename A1>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
explicit NiceMock(const A1& a1) : MockClass(a1) {
|
|
|
|
|
::testing::Mock::AllowUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
template <typename A1, typename A2>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
NiceMock(const A1& a1, const A2& a2) : MockClass(a1, a2) {
|
|
|
|
|
::testing::Mock::AllowUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
NiceMock(const A1& a1, const A2& a2, const A3& a3) : MockClass(a1, a2, a3) {
|
|
|
|
|
::testing::Mock::AllowUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4>
|
|
|
|
|
NiceMock(const A1& a1, const A2& a2, const A3& a3,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A4& a4) : MockClass(a1, a2, a3, a4) {
|
|
|
|
|
::testing::Mock::AllowUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5>
|
|
|
|
|
NiceMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A5& a5) : MockClass(a1, a2, a3, a4, a5) {
|
|
|
|
|
::testing::Mock::AllowUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6>
|
|
|
|
|
NiceMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A5& a5, const A6& a6) : MockClass(a1, a2, a3, a4, a5, a6) {
|
|
|
|
|
::testing::Mock::AllowUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6, typename A7>
|
|
|
|
|
NiceMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
|
|
|
|
const A5& a5, const A6& a6, const A7& a7) : MockClass(a1, a2, a3, a4, a5,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
a6, a7) {
|
|
|
|
|
::testing::Mock::AllowUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6, typename A7, typename A8>
|
|
|
|
|
NiceMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
|
|
|
|
const A5& a5, const A6& a6, const A7& a7, const A8& a8) : MockClass(a1,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
a2, a3, a4, a5, a6, a7, a8) {
|
|
|
|
|
::testing::Mock::AllowUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6, typename A7, typename A8, typename A9>
|
|
|
|
|
NiceMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
|
|
|
|
const A5& a5, const A6& a6, const A7& a7, const A8& a8,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A9& a9) : MockClass(a1, a2, a3, a4, a5, a6, a7, a8, a9) {
|
|
|
|
|
::testing::Mock::AllowUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6, typename A7, typename A8, typename A9, typename A10>
|
|
|
|
|
NiceMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
|
|
|
|
const A5& a5, const A6& a6, const A7& a7, const A8& a8, const A9& a9,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A10& a10) : MockClass(a1, a2, a3, a4, a5, a6, a7, a8, a9, a10) {
|
|
|
|
|
::testing::Mock::AllowUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
2018-04-05 20:09:17 +00:00
|
|
|
#endif // GTEST_LANG_CXX11
|
2009-12-23 00:13:23 +00:00
|
|
|
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
~NiceMock() {
|
|
|
|
|
::testing::Mock::UnregisterCallReaction(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
|
|
|
|
|
2009-12-23 00:13:23 +00:00
|
|
|
private:
|
|
|
|
|
GTEST_DISALLOW_COPY_AND_ASSIGN_(NiceMock);
|
2008-12-10 05:08:54 +00:00
|
|
|
};
|
|
|
|
|
|
2013-03-01 01:54:22 +00:00
|
|
|
template <class MockClass>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
class NaggyMock : public MockClass {
|
2013-03-01 01:54:22 +00:00
|
|
|
public:
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
NaggyMock() : MockClass() {
|
|
|
|
|
::testing::Mock::WarnUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2018-04-05 20:09:17 +00:00
|
|
|
|
|
|
|
|
#if GTEST_LANG_CXX11
|
2018-04-12 18:00:38 +00:00
|
|
|
// Ideally, we would inherit base class's constructors through a using
|
|
|
|
|
// declaration, which would preserve their visibility. However, many existing
|
|
|
|
|
// tests rely on the fact that current implementation reexports protected
|
|
|
|
|
// constructors as public. These tests would need to be cleaned up first.
|
|
|
|
|
|
2018-04-05 20:09:17 +00:00
|
|
|
// Single argument constructor is special-cased so that it can be
|
|
|
|
|
// made explicit.
|
|
|
|
|
template <typename A>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
explicit NaggyMock(A&& arg) : MockClass(std::forward<A>(arg)) {
|
|
|
|
|
::testing::Mock::WarnUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2018-04-05 20:09:17 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename... An>
|
|
|
|
|
NaggyMock(A1&& arg1, A2&& arg2, An&&... args)
|
|
|
|
|
: MockClass(std::forward<A1>(arg1), std::forward<A2>(arg2),
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
std::forward<An>(args)...) {
|
|
|
|
|
::testing::Mock::WarnUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2018-04-05 20:09:17 +00:00
|
|
|
#else
|
|
|
|
|
// C++98 doesn't have variadic templates, so we have to define one
|
|
|
|
|
// for each arity.
|
2013-03-01 01:54:22 +00:00
|
|
|
template <typename A1>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
explicit NaggyMock(const A1& a1) : MockClass(a1) {
|
|
|
|
|
::testing::Mock::WarnUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2013-03-01 01:54:22 +00:00
|
|
|
template <typename A1, typename A2>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
NaggyMock(const A1& a1, const A2& a2) : MockClass(a1, a2) {
|
|
|
|
|
::testing::Mock::WarnUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2013-03-01 01:54:22 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
NaggyMock(const A1& a1, const A2& a2, const A3& a3) : MockClass(a1, a2, a3) {
|
|
|
|
|
::testing::Mock::WarnUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2013-03-01 01:54:22 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4>
|
|
|
|
|
NaggyMock(const A1& a1, const A2& a2, const A3& a3,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A4& a4) : MockClass(a1, a2, a3, a4) {
|
|
|
|
|
::testing::Mock::WarnUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2013-03-01 01:54:22 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5>
|
|
|
|
|
NaggyMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A5& a5) : MockClass(a1, a2, a3, a4, a5) {
|
|
|
|
|
::testing::Mock::WarnUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2013-03-01 01:54:22 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6>
|
|
|
|
|
NaggyMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A5& a5, const A6& a6) : MockClass(a1, a2, a3, a4, a5, a6) {
|
|
|
|
|
::testing::Mock::WarnUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2013-03-01 01:54:22 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6, typename A7>
|
|
|
|
|
NaggyMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
|
|
|
|
const A5& a5, const A6& a6, const A7& a7) : MockClass(a1, a2, a3, a4, a5,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
a6, a7) {
|
|
|
|
|
::testing::Mock::WarnUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2013-03-01 01:54:22 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6, typename A7, typename A8>
|
|
|
|
|
NaggyMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
|
|
|
|
const A5& a5, const A6& a6, const A7& a7, const A8& a8) : MockClass(a1,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
a2, a3, a4, a5, a6, a7, a8) {
|
|
|
|
|
::testing::Mock::WarnUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2013-03-01 01:54:22 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6, typename A7, typename A8, typename A9>
|
|
|
|
|
NaggyMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
|
|
|
|
const A5& a5, const A6& a6, const A7& a7, const A8& a8,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A9& a9) : MockClass(a1, a2, a3, a4, a5, a6, a7, a8, a9) {
|
|
|
|
|
::testing::Mock::WarnUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2013-03-01 01:54:22 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6, typename A7, typename A8, typename A9, typename A10>
|
|
|
|
|
NaggyMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
|
|
|
|
const A5& a5, const A6& a6, const A7& a7, const A8& a8, const A9& a9,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A10& a10) : MockClass(a1, a2, a3, a4, a5, a6, a7, a8, a9, a10) {
|
|
|
|
|
::testing::Mock::WarnUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2013-03-01 01:54:22 +00:00
|
|
|
|
2018-04-05 20:09:17 +00:00
|
|
|
#endif // GTEST_LANG_CXX11
|
2013-03-01 01:54:22 +00:00
|
|
|
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
~NaggyMock() {
|
|
|
|
|
::testing::Mock::UnregisterCallReaction(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
|
|
|
|
|
2013-03-01 01:54:22 +00:00
|
|
|
private:
|
|
|
|
|
GTEST_DISALLOW_COPY_AND_ASSIGN_(NaggyMock);
|
|
|
|
|
};
|
|
|
|
|
|
2018-04-05 20:09:17 +00:00
|
|
|
template <class MockClass>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
class StrictMock : public MockClass {
|
2008-12-10 05:08:54 +00:00
|
|
|
public:
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
StrictMock() : MockClass() {
|
|
|
|
|
::testing::Mock::FailUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2018-04-05 20:09:17 +00:00
|
|
|
|
|
|
|
|
#if GTEST_LANG_CXX11
|
2018-04-12 18:00:38 +00:00
|
|
|
// Ideally, we would inherit base class's constructors through a using
|
|
|
|
|
// declaration, which would preserve their visibility. However, many existing
|
|
|
|
|
// tests rely on the fact that current implementation reexports protected
|
|
|
|
|
// constructors as public. These tests would need to be cleaned up first.
|
|
|
|
|
|
2018-04-05 20:09:17 +00:00
|
|
|
// Single argument constructor is special-cased so that it can be
|
|
|
|
|
// made explicit.
|
|
|
|
|
template <typename A>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
explicit StrictMock(A&& arg) : MockClass(std::forward<A>(arg)) {
|
|
|
|
|
::testing::Mock::FailUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2018-04-05 20:09:17 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename... An>
|
|
|
|
|
StrictMock(A1&& arg1, A2&& arg2, An&&... args)
|
|
|
|
|
: MockClass(std::forward<A1>(arg1), std::forward<A2>(arg2),
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
std::forward<An>(args)...) {
|
|
|
|
|
::testing::Mock::FailUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2018-04-05 20:09:17 +00:00
|
|
|
#else
|
|
|
|
|
// C++98 doesn't have variadic templates, so we have to define one
|
|
|
|
|
// for each arity.
|
2008-12-10 05:08:54 +00:00
|
|
|
template <typename A1>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
explicit StrictMock(const A1& a1) : MockClass(a1) {
|
|
|
|
|
::testing::Mock::FailUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
template <typename A1, typename A2>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
StrictMock(const A1& a1, const A2& a2) : MockClass(a1, a2) {
|
|
|
|
|
::testing::Mock::FailUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3>
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
StrictMock(const A1& a1, const A2& a2, const A3& a3) : MockClass(a1, a2, a3) {
|
|
|
|
|
::testing::Mock::FailUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4>
|
|
|
|
|
StrictMock(const A1& a1, const A2& a2, const A3& a3,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A4& a4) : MockClass(a1, a2, a3, a4) {
|
|
|
|
|
::testing::Mock::FailUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5>
|
|
|
|
|
StrictMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A5& a5) : MockClass(a1, a2, a3, a4, a5) {
|
|
|
|
|
::testing::Mock::FailUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6>
|
|
|
|
|
StrictMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A5& a5, const A6& a6) : MockClass(a1, a2, a3, a4, a5, a6) {
|
|
|
|
|
::testing::Mock::FailUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6, typename A7>
|
|
|
|
|
StrictMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
|
|
|
|
const A5& a5, const A6& a6, const A7& a7) : MockClass(a1, a2, a3, a4, a5,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
a6, a7) {
|
|
|
|
|
::testing::Mock::FailUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6, typename A7, typename A8>
|
|
|
|
|
StrictMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
|
|
|
|
const A5& a5, const A6& a6, const A7& a7, const A8& a8) : MockClass(a1,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
a2, a3, a4, a5, a6, a7, a8) {
|
|
|
|
|
::testing::Mock::FailUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6, typename A7, typename A8, typename A9>
|
|
|
|
|
StrictMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
|
|
|
|
const A5& a5, const A6& a6, const A7& a7, const A8& a8,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A9& a9) : MockClass(a1, a2, a3, a4, a5, a6, a7, a8, a9) {
|
|
|
|
|
::testing::Mock::FailUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
|
|
|
|
template <typename A1, typename A2, typename A3, typename A4, typename A5,
|
|
|
|
|
typename A6, typename A7, typename A8, typename A9, typename A10>
|
|
|
|
|
StrictMock(const A1& a1, const A2& a2, const A3& a3, const A4& a4,
|
|
|
|
|
const A5& a5, const A6& a6, const A7& a7, const A8& a8, const A9& a9,
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
const A10& a10) : MockClass(a1, a2, a3, a4, a5, a6, a7, a8, a9, a10) {
|
|
|
|
|
::testing::Mock::FailUninterestingCalls(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
2008-12-10 05:08:54 +00:00
|
|
|
|
2018-04-05 20:09:17 +00:00
|
|
|
#endif // GTEST_LANG_CXX11
|
2009-12-23 00:13:23 +00:00
|
|
|
|
Remove multiple inheritance from "unintesting call" mock classes.
Internal CL 156157936, which was published in commit
fe402c27790ff1cc9a7e17c5d0aea4ebe7fd8a71, introduced undefined behavior
by casting a base class (internal::{Naggy,Nice,Strict}Base<MockClass>,
using the curiously recurring template pattern) pointer to a derived
class ({Naggy,Nice,Strict}Mock<MockClass>), in the base class'
constructor. At that point, the object isn't guaranteed to have taken on
the shape of the derived class, and casting is undefined behavior.
The undefined behavior was caught by Chrome's CFI build bot [1], and
prevents rolling googletest past that commit / CL.
This commit simplifies the {Naggy,Nice,Strict}Mock class hierarchy in
a way that removes the undefined behavior.
[1] https://www.chromium.org/developers/testing/control-flow-integrity
2018-04-10 04:57:54 +00:00
|
|
|
~StrictMock() {
|
|
|
|
|
::testing::Mock::UnregisterCallReaction(
|
|
|
|
|
internal::ImplicitCast_<MockClass*>(this));
|
|
|
|
|
}
|
|
|
|
|
|
2009-12-23 00:13:23 +00:00
|
|
|
private:
|
|
|
|
|
GTEST_DISALLOW_COPY_AND_ASSIGN_(StrictMock);
|
2008-12-10 05:08:54 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
// The following specializations catch some (relatively more common)
|
|
|
|
|
// user errors of nesting nice and strict mocks. They do NOT catch
|
|
|
|
|
// all possible errors.
|
|
|
|
|
|
2013-03-01 01:54:22 +00:00
|
|
|
// These specializations are declared but not defined, as NiceMock,
|
|
|
|
|
// NaggyMock, and StrictMock cannot be nested.
|
|
|
|
|
|
2008-12-10 05:08:54 +00:00
|
|
|
template <typename MockClass>
|
|
|
|
|
class NiceMock<NiceMock<MockClass> >;
|
|
|
|
|
template <typename MockClass>
|
2013-03-01 01:54:22 +00:00
|
|
|
class NiceMock<NaggyMock<MockClass> >;
|
|
|
|
|
template <typename MockClass>
|
2008-12-10 05:08:54 +00:00
|
|
|
class NiceMock<StrictMock<MockClass> >;
|
2013-03-01 01:54:22 +00:00
|
|
|
|
|
|
|
|
template <typename MockClass>
|
|
|
|
|
class NaggyMock<NiceMock<MockClass> >;
|
|
|
|
|
template <typename MockClass>
|
|
|
|
|
class NaggyMock<NaggyMock<MockClass> >;
|
|
|
|
|
template <typename MockClass>
|
|
|
|
|
class NaggyMock<StrictMock<MockClass> >;
|
|
|
|
|
|
2008-12-10 05:08:54 +00:00
|
|
|
template <typename MockClass>
|
|
|
|
|
class StrictMock<NiceMock<MockClass> >;
|
|
|
|
|
template <typename MockClass>
|
2013-03-01 01:54:22 +00:00
|
|
|
class StrictMock<NaggyMock<MockClass> >;
|
|
|
|
|
template <typename MockClass>
|
2008-12-10 05:08:54 +00:00
|
|
|
class StrictMock<StrictMock<MockClass> >;
|
|
|
|
|
|
|
|
|
|
} // namespace testing
|
|
|
|
|
|
|
|
|
|
#endif // GMOCK_INCLUDE_GMOCK_GMOCK_GENERATED_NICE_STRICT_H_
|
