Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

need to fail when no test is defined #144

Open
GoogleCodeExporter opened this issue Jul 31, 2015 · 4 comments
Open

need to fail when no test is defined #144

GoogleCodeExporter opened this issue Jul 31, 2015 · 4 comments
Labels
auto-migrated OpSys-All Priority-Medium Type-Enhancement

Comments

@GoogleCodeExporter
Copy link 

Sometimes a user links gtest_main.cc with the wrong files and no test is
defined.  The test programs will pass in this case since there's no
assertion failure.

Having no test defined most likely is a user error.  JUnit has been
reporting it as a failure for years, and the users like this.  We should do
the same.

Original issue reported on code.google.com by [email protected] on 4 May 2009 at 5:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated OpSys-All Priority-Medium Type-Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter