[racket-users] Organizing tests in project

2020-03-17 Thread Siddhartha Kasivajhula
Hi, I'm attempting to organize tests in my package into subfolders/modules instead of having them in a giant main.rkt test submodule, but am running into some issues and was hoping for some advice on the best way to do it. I think the primary issue is related to source compilation order in raco, bu

Re: [racket-users] Organizing tests

2015-04-19 Thread WarGrey Gyoudmon Ju
Thank you Matthias This suggestion has enlightened me. I did not figure out a good way to filter tests based on their types. and, Konrad. I have a makefile.rkt to help me (and potential cooperators) build the system. The *scribble/lp* plays an important role in my development process not only beca

Re: [racket-users] Organizing tests

2015-04-19 Thread Greg Hendershott
That's the --submodule or -s flag. I did `raco help test` just now and discovered even more options than I remembered. Including fun things like running tests in parallel, printing a summary table, and so on. racket-mode has a couple features related to tests and coverage. They currently assume

Re: [racket-users] Organizing tests

2015-04-17 Thread Konrad Hinsen
Thanks to Matthias, John, and Greg for their suggestions! I explored the raco documentation in more detail and I will try to come up with some good solution. My main goal is to have convenient modes of operation: 1) Developers (currently me) should be able to run easily the subset of tests that

Re: [racket-users] Organizing tests

2015-04-16 Thread 'John Clements' via users-redirect
On Apr 16, 2015, at 3:17 AM, Konrad Hinsen wrote: > 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

Re: [racket-users] Organizing tests

2015-04-16 Thread Matthias Felleisen
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

[racket-users] Organizing tests

2015-04-16 Thread Konrad Hinsen
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 ni