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.

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

!!! BREAKING CHANGE (console output only) !!! - Emulate the error/warning format emitted by native compiler gcc/clang/msvc when printing test failures in the log #123

Closed
obfuscated opened this issue Apr 11, 2018 · 0 comments

Comments

@obfuscated
Copy link

This is a critical feature of a test framework.

The current output is something like this:
test_something.cpp(99) ERROR!

My IDE doesn't know about this format so it doesn't show it in the list of errors.
Other testing frameworks emulate the output of the native compiler. This allows them to integrate easily with IDEs.

So they produce something like:
test_something.cpp:99: error: Test blabla failed
When running on Unix and the equivalent recognized by MS VStudio when running on windows.

Generally there should be an option what output is expected.

@onqtam onqtam changed the title Emulate the error/warning format emitted by native compiler gcc/clang/msvc when printing test failures in the log !!! BREAKING CHANGE !!! - Emulate the error/warning format emitted by native compiler gcc/clang/msvc when printing test failures in the log May 9, 2018
@onqtam onqtam changed the title !!! BREAKING CHANGE !!! - Emulate the error/warning format emitted by native compiler gcc/clang/msvc when printing test failures in the log !!! BREAKING CHANGE (console output only) !!! - Emulate the error/warning format emitted by native compiler gcc/clang/msvc when printing test failures in the log May 10, 2018
onqtam added a commit that referenced this issue May 10, 2018
…ut with :n: around line numbers and other compilers output with (n) - there is also a documented option for this. Also changed lots of code - thank god I moved to streams!

!!! output not regenerated yet - next commit!
onqtam added a commit that referenced this issue May 10, 2018
@onqtam onqtam closed this as completed in 7907692 May 10, 2018
onqtam added a commit that referenced this issue May 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant