redirect command to output #2
Conversation
(cherry picked from commit 60a7b19)
jmecosta
force-pushed
the
redirect-output
branch
from
267b316 to
f92d4d9
Compare
|
Hello, First, I am sorry for my very late answer. I made a break on OpenCppCoverage Plugin to work on OpenCppCoverage and then on other projects. Now I am back on this project! I am also not fully happy with the current solution that displays a message at the end of the coverage. |
|
OK, weird that some users have this use case, since the window is quite
annoying. Maybe make it configurable?
…On Tue, 8 Aug 2017, 15:55 OpenCppCoverage, ***@***.***> wrote:
Hello,
First, I am sorry for my very late answer. I make a break on *OpenCppCoverage
Plugin* to work on *OpenCppCoverage* and then on other projects. Now I am
back on this project!
I am also not fully happy with the current solution that displays a
message at the end of the coverage.
Before doing this, I tried to redirect the message to the output window as
you did. Unfortunately, output window seems to not support standard input
redirection.
As some users may use standard input in their program, we cannot redirect
message to the output window.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA_jyCXNyphAMsmgf7Oyio1LtloFhCYEks5sWGjDgaJpZM4KeGkP>
.
|
|
Hello, My main usage of OpenCppCoverage plugin is running unit tests with GTest. Do you have an use case in which the console is really annoying? Even when running an application, it is useful to see if there is an error at the end. I try to design OpenCppCoverage to be easy to use and avoid adding several ways of doing the same thing except if there is a noticeable benefit. OpenCppCoverage |
|
we are using also gtest and we use the visual studio test adapter https://marketplace.visualstudio.com/items?itemName=ChristianSoltenborn.GoogleTestAdapter and there are no pop ups anywhere. maybe thats the difference. the visual studio experience when in comes for testing and coverage tools in typical tools do not show popups, they run in background so they dont take your attention from what your doing. anyway this is just a difference to other coverage tools and test frameworks we use. if you think this is the way, then please close. thanks |
|
Hello, Thank you for this feedback. Indeed, when you run a test from Test Explorer, you do not want to have any windows because you know whether your test failed or not. Do you know if it is possible to hook this plugin? I had a very quick look and do not see anything obvious. OpenCppCoverage |
|
Yes that's is the general develor workflow, so it really feels unnatural to
get those pop-ups ;) and all the output actually goes into the output
window also
Now to your question, I saw at some point some discussion in the opencover
extension regarding this, but ensure if they have added the support. so
far I haven't seen any real implementation of this :(
…On Sat, 19 Aug 2017, 15:54 OpenCppCoverage ***@***.***> wrote:
Hello,
Thank you for this feedback. Indeed, when you run a test from *Test
Explorer*, you do not want to have any windows because you know whether
your test failed or not.
Ideally, we would like to run the coverage from *Test Explorer* and do
not display any windows.
Do you know if it is possible to hook this plugin? I had a very quick look
and do not see anything obvious.
OpenCppCoverage
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA_jyD3uWbiPkVpHawfiJhrjaLAuH4rcks5sZtsAgaJpZM4KeGkP>
.
|
|
Also I'm more than happy to use the Explorer to run tests, and then press
produce coverage to see coverage and in this case the pop up is not needed
and in principle as you said the failures are already in the test explorer
…On Sat, 19 Aug 2017, 16:00 Jorge Costa ***@***.***> wrote:
Yes that's is the general develor workflow, so it really feels unnatural
to get those pop-ups ;) and all the output actually goes into the output
window also
Now to your question, I saw at some point some discussion in the opencover
extension regarding this, but ensure if they have added the support. so
far I haven't seen any real implementation of this :(
On Sat, 19 Aug 2017, 15:54 OpenCppCoverage ***@***.***>
wrote:
> Hello,
>
> Thank you for this feedback. Indeed, when you run a test from *Test
> Explorer*, you do not want to have any windows because you know whether
> your test failed or not.
> Ideally, we would like to run the coverage from *Test Explorer* and do
> not display any windows.
>
> Do you know if it is possible to hook this plugin? I had a very quick
> look and do not see anything obvious.
>
> OpenCppCoverage
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#2 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AA_jyD3uWbiPkVpHawfiJhrjaLAuH4rcks5sZtsAgaJpZM4KeGkP>
> .
>
|
|
Hello, I am working now on the command line version of OpenCppCoverage and as this developement is not trivial, I have just had it to the roadmap. OpenCppCoverage |
2 participants
is this something you can use? redirect tool output to output window and send termination signal once its done so the window requesting input will not show up?