Hi,
Sean has left the following comment at Create numerics library (LIBBN) API
unit test ... for list.c
http://www.google-melange.com/gci/task/view/google/gci2012/8000211:
it depends
Large projects (regardless of language) can take a while to compile, but
there's almost always ways to build subsections as-needed MUCH faster. In
your case, you can go to src/libbn in your build directory ("cd src/libbn")
and run make there. That will just compile libbn and the tests.
The libbu tests are easier to understand and written better. A couple of
the libbn tests are utterly terrible examples to follow and will probably
be removed or changed at some point in the future. Feel free to look at
them as an example of what not to do.
You do write the test rather free-form. Just make it easy to read and
understand. Try to minimize duplication. That's where the libbu examples
are good. From a testing perspective, all that will matter is the return
code from the application (!0 => failure).
Your understanding of the test runner and test definition is accurate.
Greetings,
The Google Open Source Programs Team
---
You are receiving this message because you are subscribed to Create
numerics library (LIBBN) API unit test ... for list.c.
To stop receiving these messages, go to:
http://www.google-melange.com/gci/task/view/google/gci2012/8000211.
------------------------------------------------------------------------------
Keep yourself connected to Go Parallel:
VERIFY Test and improve your parallel project with help from experts
and peers. http://goparallel.sourceforge.net
_______________________________________________
BRL-CAD Tracker mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-tracker
