[Solved][ish] QTest output not showing in vs2013 output window
Previously, with Qt5.1, in vs2013 IDE, I had my project set up to run the test exe as a post-build event (in the vs2013 settings) and the QTest console output would appear in the vs Output-Build window. Thus it was a pretty convenient one command process to build and test.
Now I've (finally) migrated to Qt5.3, the QTest console output doesn't appear. I don't know where it goes. I get output from a couple of file copies that I also do as part of the "post-build event". And I'm pretty sure the test is running, since there's a pause in the build window output (unless I remove the command to run the test). Of course the test itself runs fine if I run it independently - but that means pressing another button ! (shock !).
So, of course this is a no biggy, but if anyone knows what changed, or what I might do to fix it easily... (naturally, had it never worked in the first place, I would never ask, but since it was working before it rankles somewhat...)
Edit:- Well, I've got it working now by sending the QTest output to a file, then calling "type output.txt". But it's a bit of a workaround if you ask me
Sounds like a regression, you should check the "bug report system":http://bugreports.qt-project.org to see if it's something known
bq. Sounds like a regression
Right. I couldn't see anything, so I logged it as a bug. I suspect not so many people are using both MSVC and TestLib :-)
There's a very faint bell ringing in my head about windows and stdout behaving oddly, but that was many years ago...
Might be indeed
Could you also share the bug report link ? So if others hit the same problem they may find it more easily
That bell must not be false
Sorry - yes - the link is "here":https://bugreports.qt-project.org/browse/QTBUG-41239http://
bq. bell must not be false
You don't know my Brain like I do... Still, Windows.....
The thing is that you're not alone with this one faint bell :)
In case anyone else is having this kind of problem, take a look at the bug report "here":https://bugreports.qt-project.org/browse/QTBUG-41239
If you sort out a nicer fix (i.e. you know how to redirect std streams in Windows) then let me know :-)