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

error when no tests ran #1158

Closed
dvirtz opened this issue Jan 21, 2018 · 0 comments · Fixed by #1180
Closed

error when no tests ran #1158

dvirtz opened this issue Jan 21, 2018 · 0 comments · Fixed by #1180

Comments

@dvirtz
Copy link
Contributor

dvirtz commented Jan 21, 2018

Description

Is there an option to get an error when no tests ran? I thought that -w NoAssertions would do this but it doesn't.
I use the new catch_discover_tests script and it doesn't seem to handle spaces in test names correctly so it runs the test executable with invalid names but the tests pass as no tests ran.

Steps to reproduce

Test -w NoAssertions INVALID_TEST_NAME

Extra information

  • Catch version: v2.0.1
  • Operating System: Windows 10
  • Compiler+version: VS 2017 15.6
dvirtz added a commit to dvirtz/Catch that referenced this issue Feb 8, 2018
@dvirtz
add option to warn when no tests ran
e184eaa 
resolves catchorg#1158
@dvirtz dvirtz mentioned this issue Feb 8, 2018
Merged
horenmar pushed a commit that referenced this issue Feb 9, 2018
@dvirtz @horenmar
add option to warn when no tests ran
fb63b6d 
resolves #1158
horenmar pushed a commit that referenced this issue Feb 9, 2018
@dvirtz @horenmar
Add option to warn when no tests ran
355b3f9 
Closes #1158
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add option to warn when no tests ran dvirtz/Catch
1 participant
@dvirtz