search

ddavis2speedray / googletest

Automatically exported from code.google.com/p/googletest
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

GoogleTestPrimer doc confusion #299

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
IMPORTANT NOTE: Before you create an issue, please first search the issue
tracker to see if it has been reported.  If you believe it's a new issue,
please send it to
googletestframework@googlegroups.com (you need to first join the
group at
http://groups.google.com/group/googletestframework).  You'll get an answer
much faster that way, as the issue tracker is NOT regularly monitored.

When creating a new issue, please provide the information asked for below.
The more detailed your answer, the more likely the bug will be fixed.

Finally, Google Test is community-supported now, meaning that no one
officially works on it, and everyone is expected to help.  It will be
appreciated if you investigate the problem yourself and contribute a patch
in addition to creating the issue.

What steps will reproduce the problem?
1. go to 
http://code.google.com/p/googletest/wiki/GoogleTestPrimer#Important_note_for_Vis
ual_C++_users
2. read "The general conclusion here is: make your life easier - do not write 
your tests in libraries! "
3. ????

What is the expected output? What do you see instead?
4. If you are writing a library, this statement is quite confusing.
Particularly when you do not have the source to the intended library  loading 
executable. I think the sentence could be removed altogether.

It might be less confusing if instead it stated: "If you have access to the 
executable's source it is less complicated to write your tests there than in a 
linked library. If you do not have source access and you must write tests 
within a linked library, googletest library static/dynamic settings must match 
your linked library settings." 

What version of Google Test are you using? On what operating system?

Please provide any additional information below, such as a code snippet.

Original issue reported on code.google.com by eliasmac...@yahoo.com on 29 Jun 2010 at 11:16

GoogleCodeExporter commented 9 years ago 
The code you are writing may very well be in a library, but our recommendation 
still stands: we recommend putting tests for it into an executable. You library 
may be linked to that executable.

Original comment by vladlosev on 9 Jul 2010 at 7:41