-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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.
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
Add a way to identify the executable as a google-test? #1121
Comments
Looks stale |
Hoe does still look stale? Can we just add it? Its loe hanging fruit |
@janwilmans please feel free to open a PR for consideration |
@gennadiycivil last we talked I think you left the googletest team, are you back now? |
@janwilmans you may be confusing me with @BillyDonahue :-) |
oh, excuse me please :) |
No worries whatsoever :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I propose to standardise a command-line option to identify the executable as a certain kind of test:
I will propose this to boost.test and catch as well.
see https://github.com/janwilmans/LibIdentify
The text was updated successfully, but these errors were encountered: