Yep, a test suite is fine, and making it a separate project as well.
-hk
On Mon, Aug 27, 2018 at 11:08 AM Don Morrison dfm@ringing.org wrote:
On Mon, Aug 27, 2018 at 9:29 AM Ken Tilton kentilton@gmail.com wrote:
Use one package per library. If you want to document your library,
document the public bits.
While by and large this does seem to work well, there is often value in having a second package for the tests, that uses the library’s main package. Otherwise you can accidentally use internal symbols in your tests in ways not publicly exposed to real users of your library; on those occasions when you really do need access to internal symbols in your tests it seems better to have to explicitly import or qualify them.
-- Don Morrison dfm@ringing.org “Each of these views has been held by an important segment of the cognitive science community, and the two segments do not often communicate with each other, except sometimes to quarrel.” – Herbert Simon, /Models of My Life/