Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
googletest
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Chen Yisong
googletest
Commits
96ddffe8
Commit
96ddffe8
authored
Jun 18, 2014
by
kosak
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Reduce the number of occurrences of gendered pronouns in gtest.
parent
21ee8a2e
Hide whitespace changes
Inline
Side-by-side
Showing
6 changed files
with
25 additions
and
25 deletions
+25
-25
gtest.h
include/gtest/gtest.h
+11
-11
gtest-death-test.cc
src/gtest-death-test.cc
+3
-3
gtest-internal-inl.h
src/gtest-internal-inl.h
+1
-1
gtest-port.cc
src/gtest-port.cc
+3
-3
gtest-test-part.cc
src/gtest-test-part.cc
+3
-3
gtest.cc
src/gtest.cc
+4
-4
No files found.
include/gtest/gtest.h
View file @
96ddffe8
...
...
@@ -70,14 +70,14 @@
// class ::string, which has the same interface as ::std::string, but
// has a different implementation.
//
//
The user
can define GTEST_HAS_GLOBAL_STRING to 1 to indicate that
//
You
can define GTEST_HAS_GLOBAL_STRING to 1 to indicate that
// ::string is available AND is a distinct type to ::std::string, or
// define it to 0 to indicate otherwise.
//
// If
the user's ::std::string and ::string are the same class due to
//
aliasing, he
should define GTEST_HAS_GLOBAL_STRING to 0.
// If
::std::string and ::string are the same class on your platform
//
due to aliasing, you
should define GTEST_HAS_GLOBAL_STRING to 0.
//
// If
the user doesn'
t define GTEST_HAS_GLOBAL_STRING, it is defined
// If
you do no
t define GTEST_HAS_GLOBAL_STRING, it is defined
// heuristically.
namespace
testing
{
...
...
@@ -455,17 +455,17 @@ class GTEST_API_ Test {
// Uses a GTestFlagSaver to save and restore all Google Test flags.
const
internal
::
GTestFlagSaver
*
const
gtest_flag_saver_
;
// Often a user mis
-
spells SetUp() as Setup() and spends a long time
// Often a user misspells SetUp() as Setup() and spends a long time
// wondering why it is never called by Google Test. The declaration of
// the following method is solely for catching such an error at
// compile time:
//
// - The return type is deliberately chosen to be not void, so it
// will be a conflict if
a user declares void Setup() in his test
// fixture.
// will be a conflict if
void Setup() is declared in the user's
//
test
fixture.
//
// - This method is private, so it will be another compiler error
// if
a user calls it from hi
s test fixture.
// if
the method is called from the user'
s test fixture.
//
// DO NOT OVERRIDE THIS FUNCTION.
//
...
...
@@ -948,7 +948,7 @@ class GTEST_API_ TestCase {
};
// An Environment object is capable of setting up and tearing down an
// environment.
The user should subclass this to define his
own
// environment.
You should subclass this to define your
own
// environment(s).
//
// An Environment object does the set-up and tear-down in virtual
...
...
@@ -2231,8 +2231,8 @@ bool StaticAssertTypeEq() {
// The convention is to end the test case name with "Test". For
// example, a test case for the Foo class can be named FooTest.
//
// T
he user should put his test code between braces after using this
// macro. Example:
// T
est code should appear between braces after an invocation of
//
this
macro. Example:
//
// TEST(FooTest, InitializesCorrectly) {
// Foo foo;
...
...
src/gtest-death-test.cc
View file @
96ddffe8
...
...
@@ -68,9 +68,9 @@
// Indicates that this translation unit is part of Google Test's
// implementation. It must come before gtest-internal-inl.h is
// included, or there will be a compiler error. This trick
i
s to
// prevent
a user from accidentally including gtest-internal-inl.h in
//
hi
s code.
// included, or there will be a compiler error. This trick
exist
s to
// prevent
the accidental inclusion of gtest-internal-inl.h in the
//
user'
s code.
#define GTEST_IMPLEMENTATION_ 1
#include "src/gtest-internal-inl.h"
#undef GTEST_IMPLEMENTATION_
...
...
src/gtest-internal-inl.h
View file @
96ddffe8
...
...
@@ -40,7 +40,7 @@
// GTEST_IMPLEMENTATION_ is defined to 1 iff the current translation unit is
// part of Google Test's implementation; otherwise it's undefined.
#if !GTEST_IMPLEMENTATION_
//
A user is trying to include this from his code -
just say no.
//
If this file is included from the user's code,
just say no.
# error "gtest-internal-inl.h is part of Google Test's internal implementation."
# error "It must not be included except by Google Test itself."
#endif // GTEST_IMPLEMENTATION_
...
...
src/gtest-port.cc
View file @
96ddffe8
...
...
@@ -64,9 +64,9 @@
// Indicates that this translation unit is part of Google Test's
// implementation. It must come before gtest-internal-inl.h is
// included, or there will be a compiler error. This trick
i
s to
// prevent
a user from accidentally including gtest-internal-inl.h in
//
hi
s code.
// included, or there will be a compiler error. This trick
exist
s to
// prevent
the accidental inclusion of gtest-internal-inl.h in the
//
user'
s code.
#define GTEST_IMPLEMENTATION_ 1
#include "src/gtest-internal-inl.h"
#undef GTEST_IMPLEMENTATION_
...
...
src/gtest-test-part.cc
View file @
96ddffe8
...
...
@@ -35,9 +35,9 @@
// Indicates that this translation unit is part of Google Test's
// implementation. It must come before gtest-internal-inl.h is
// included, or there will be a compiler error. This trick
i
s to
// prevent
a user from accidentally including gtest-internal-inl.h in
//
hi
s code.
// included, or there will be a compiler error. This trick
exist
s to
// prevent
the accidental inclusion of gtest-internal-inl.h in the
//
user'
s code.
#define GTEST_IMPLEMENTATION_ 1
#include "src/gtest-internal-inl.h"
#undef GTEST_IMPLEMENTATION_
...
...
src/gtest.cc
View file @
96ddffe8
...
...
@@ -1962,8 +1962,8 @@ bool Test::HasSameFixtureClass() {
const
bool
this_is_TEST
=
this_fixture_id
==
internal
::
GetTestTypeId
();
if
(
first_is_TEST
||
this_is_TEST
)
{
//
The user mixed TEST and TEST_F in this test case - we'll tell
//
him/her how to fix it
.
//
Both TEST and TEST_F appear in same test case, which is incorrect.
//
Tell the user how to fix this
.
// Gets the name of the TEST and the name of the TEST_F. Note
// that first_is_TEST and this_is_TEST cannot both be true, as
...
...
@@ -1983,8 +1983,8 @@ bool Test::HasSameFixtureClass() {
<<
"want to change the TEST to TEST_F or move it to another test
\n
"
<<
"case."
;
}
else
{
// T
he user defined two fixture classes with the same name in
//
two namespaces - we'll tell him/her how to fix it
.
// T
wo fixture classes with the same name appear in two different
//
namespaces, which is not allowed. Tell the user how to fix this
.
ADD_FAILURE
()
<<
"All tests in the same test case must use the same test fixture
\n
"
<<
"class. However, in test case "
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment