Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
yangql
googletest
Commits
38611c51
Unverified
Commit
38611c51
authored
Feb 13, 2018
by
Gennadiy Civil
Committed by
GitHub
Feb 13, 2018
Browse files
Merge pull request #1457 from gennadiycivil/master
merging, cleaning up
parents
462ef92f
06972419
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
12 deletions
+12
-12
googletest/test/gtest_all_test.cc
googletest/test/gtest_all_test.cc
+12
-12
No files found.
googletest/test/gtest_all_test.cc
View file @
38611c51
...
@@ -33,15 +33,15 @@
...
@@ -33,15 +33,15 @@
//
//
// Sometimes it's desirable to build most of Google Test's own tests
// Sometimes it's desirable to build most of Google Test's own tests
// by compiling a single file. This file serves this purpose.
// by compiling a single file. This file serves this purpose.
#include "
test/
gtest-filepath_test.cc"
#include "gtest-filepath_test.cc"
#include "
test/
gtest-linked_ptr_test.cc"
#include "gtest-linked_ptr_test.cc"
#include "
test/
gtest-message_test.cc"
#include "gtest-message_test.cc"
#include "
test/
gtest-options_test.cc"
#include "gtest-options_test.cc"
#include "
test/
gtest-port_test.cc"
#include "gtest-port_test.cc"
#include "
test/
gtest_pred_impl_unittest.cc"
#include "gtest_pred_impl_unittest.cc"
#include "
test/
gtest_prod_test.cc"
#include "gtest_prod_test.cc"
#include "
test/
gtest-test-part_test.cc"
#include "gtest-test-part_test.cc"
#include "
test/
gtest-typed-test_test.cc"
#include "gtest-typed-test_test.cc"
#include "
test/
gtest-typed-test2_test.cc"
#include "gtest-typed-test2_test.cc"
#include "
test/
gtest_unittest.cc"
#include "gtest_unittest.cc"
#include "
test/
production.cc"
#include "production.cc"
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