Comments (5)
Hi,
Finally, here is my patch to solve this problem.
I've used the same trick that you used in death test macros. Thus only one
EXPECT_*
or ASSERT_* macro can be used in one line! (The same is true for ASSERT_DEATH
for
example.) I believe it is not a big restriction, however it is not for me to
decide..
I had to change the death test test, because you are using 2 EXPECT_ macro in a
death test macro which violates the new restriction. Maybe this will the
meaning of
that test also!
The format is maybe not perfect, but provides more information about the source
of
the error.
Catching is still controlled by catch_exceptions flag.
New tests implemented in gtest_unittest.cc to check the new feature.
Best regards,
Balazs
Original comment by [email protected]
on 19 Jul 2008 at 1:00
Attachments:
from googletest.
Original comment by [email protected]
on 31 Jul 2008 at 6:40
- Changed state: Started
- Added labels: OpSys-All, Priority-High, Type-Enhancement
- Removed labels: Priority-Medium, Type-Defect
from googletest.
Original comment by [email protected]
on 31 Jul 2008 at 6:40
from googletest.
Based on the complexity of the change and the likelihood of it breaking existing
code, we decided that it may not be worth it.
Original comment by [email protected]
on 5 Aug 2008 at 7:15
- Changed state: WontFix
from googletest.
I am sorry I am resurrecting this wontfix, but it sounds quite bad that it is
not possible to get the reason a test fails. It is completely opaque both on
the message output and on the debugging session, as the program exits without a
chance to check a backtrace with the debugger.
Original comment by [email protected]
on 4 Jan 2015 at 12:42
from googletest.
Related Issues (20)
- need to clean up Windows CE and Symbian related logic HOT 1
- Elapsed time for global and per testcase setup and teardown HOT 1
- Crash with /vd2 flag HOT 3
- In addition to PASS & FAIL, also add test result class SKIPPED (or similar)? HOT 4
- Provide a way to determine whether a death test is running in a child process. HOT 3
- TEST macro name conflicts with similar macro in UnitTest++ HOT 4
- Need to add samples to the Visual Studio solution. HOT 1
- EXPECT_STRCASEEQ should accept wide strings too HOT 2
- need to rename TestPartResultType enums before publishing the event listener API HOT 2
- /MT and /MD option necessary HOT 5
- all tests need to be registered before RUN_ALL_TESTS() HOT 2
- Need better test coverage of gtest-death-test.cc HOT 2
- The xml output can not be parsed by the Cruisecontrol HOT 2
- Death tests are not enabled properly on Solaris HOT 2
- close() function is not declared properly on Solaris when using death tests HOT 2
- Using death test asserts needs RE::RE(const testing::internal::RE&) copy constructor HOT 2
- Death tests are not enabled on HP-UX HOT 3
- close() function is not declared properly on HP-UX when using death tests HOT 3
- Death tests are not enabled on AIX HOT 2
- close() function is not declared properly on AIX when using death tests
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from googletest.