You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
andy.bache _at_ googlemail.com suggested:
"I have just got started with Google C++ Testing Framework and was
wondering if anyone had built or is planning to build a Google C++
Tests Add In for Visual Studio. I have used the NUnit add in with the
#Develop IDE. It runs all the tests as part of build process and
displays the results on a panel within the IDE.
I have been away from C++ for a little while and have just returned to
developing in C++ with Visual Studio and am trying to get a Unit Test
framework in place. I like the look of google tests but having it
better integrated with the IDE would be helpful.
Using the post build step to kick off unit tests is a good start but
it would be better to have the results integrated in the IDE.
I guess that I could write my own Visual Studio Add In - possibly
parsing the XML results file and displaying the results in the IDE but
I have never written on before so that would quite a bit of time and
effort and I would hate to do it if someone else already has and made
a good job of it.
If you know of anything like this or also think it would be useful get
back to me.
Cheers,"
I replied:
"Hi Andy,
Thanks for the suggestion! I think this will be something very nice to
have.
Unfortunately I don't know how to write a VS add-in either, and my
hands are full (actually more than full). Therefore I hope you or
someone interested could take the challenge to implement it and share
the result with the rest of us. Cheers!"
Original issue reported on code.google.com by shiq...@gmail.com on 29 Sep 2008 at 3:14
The text was updated successfully, but these errors were encountered:
Would you be able to do something similar to how Boost's unit testing works with
Visual Studio?
http://www.boost.org/doc/libs/1_36_0/libs/test/doc/html/utf/usage-recommendation
s/dot-net-specific.html
Boost can be setup as a post build event and any errors are then provided in
Visual
Studio's format so that a developer can click on the errors and be taken to the
code.
I don't quick know how it all works, but I've been using it for a project and
it's
been great.
I'm interested in switching to googletest, but I'm not sure if I'll get the same
functionality I have now with Boost testing.
-Paul Solt
Original comment by PaulSolt on 7 Feb 2009 at 8:44
Paul, googletest already outputs in a Visual-Studio-friendly format. If you
make
running the tests as a post-build step, you'll be able to jump to the code by
clicking on the errors. I haven't tried this myself, but I know people who did
this
and my impression is that it's easy to set up.
Original comment by zhanyong...@gmail.com on 9 Feb 2009 at 12:12
Original issue reported on code.google.com by
shiq...@gmail.com
on 29 Sep 2008 at 3:14The text was updated successfully, but these errors were encountered: