Use different names for the various test modules. At the local level, you can use module+ test. For the integration tests, you may wish to use module+ integration. Then run raco test with the parameter that takes the name of the submodule you want. (If you really want to run unit tests together with integration tests, import the former into the latter.)
-- Matthias On Apr 16, 2015, at 11:17 AM, Konrad Hinsen wrote: > Hi everyone, > > I want to put some order into my tests, but after looking at various > published Racket packages, I am not sure if there any accepted "best > practices". > > For a single module, the best approach seems to be a submodule "test" > for the test cases, which are then run by "raco test". That's nice and > works fine. > > But what I have is a collection with multiple modules. Each modules > has local tests, but there are also tests at a higher level that use > code from several modules. > > I am looking for an approach that lets me run either all tests in my > collection, or convenient subsets (e.g. one module), ideally using a > single tool such as "raco test". Any suggestions? You get bonus points > for solutions that integrate well with racket-mode in Emacs. > > Thanks in advance, > Konrad. > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
