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
c84afbea
Commit
c84afbea
authored
Apr 24, 2013
by
zhanyong.wan
Browse files
Fixes a thread annotation; updates CHANGES for 1.7.0
parent
0fac8339
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
19 additions
and
3 deletions
+19
-3
CHANGES
CHANGES
+18
-1
src/gtest.cc
src/gtest.cc
+1
-2
No files found.
CHANGES
View file @
c84afbea
Changes for 1.7.0:
Changes for 1.7.0:
TO BE WRITTEN.
* New feature: death tests are supported on OpenBSD and in iOS
simulator now.
* New feature: Test::RecordProperty() can now be used outside of the
lifespan of a test method, in which case it will be attributed to
the current test case or the test program in the XML report.
* New feature (potentially breaking): --gtest_list_tests now prints
the type parameters and value parameters for each test.
* Improvement: char pointers and char arrays are now escaped properly
in failure messages.
* Improvement: failure summary in XML reports now includes file and
line information.
* Improvement: the <testsuites> XML element now has a timestamp attribute.
* Fixed the bug where long --gtest_filter flag values are truncated in
death tests.
* Potentially breaking change: RUN_ALL_TESTS() is now implemented as a
function instead of a macro in order to work better with Clang.
* Compatibility fixes with C++ 11 and various platforms.
* Bug/warning fixes.
Changes for 1.6.0:
Changes for 1.6.0:
...
...
src/gtest.cc
View file @
c84afbea
...
@@ -3705,13 +3705,12 @@ Environment* UnitTest::AddEnvironment(Environment* env) {
...
@@ -3705,13 +3705,12 @@ Environment* UnitTest::AddEnvironment(Environment* env) {
// assertion macros (e.g. ASSERT_TRUE, EXPECT_EQ, etc) eventually call
// assertion macros (e.g. ASSERT_TRUE, EXPECT_EQ, etc) eventually call
// this to report their results. The user code should use the
// this to report their results. The user code should use the
// assertion macros instead of calling this directly.
// assertion macros instead of calling this directly.
GTEST_LOCK_EXCLUDED_
(
mutex_
)
void
UnitTest
::
AddTestPartResult
(
void
UnitTest
::
AddTestPartResult
(
TestPartResult
::
Type
result_type
,
TestPartResult
::
Type
result_type
,
const
char
*
file_name
,
const
char
*
file_name
,
int
line_number
,
int
line_number
,
const
std
::
string
&
message
,
const
std
::
string
&
message
,
const
std
::
string
&
os_stack_trace
)
{
const
std
::
string
&
os_stack_trace
)
GTEST_LOCK_EXCLUDED_
(
mutex_
)
{
Message
msg
;
Message
msg
;
msg
<<
message
;
msg
<<
message
;
...
...
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