Ah - thank you! I think I finally understand how this works. To make
sure, I query the props like this:
~/apps/racket$ ./pkgs/plt-services/meta/props get drdr:command-line
pkgs/racket-pkgs/racket-test/tests/run-automated-tests.rkt
mzc -k ~s
This tells DrDr to make sure the file compiles
All correct
On Fri, Sep 6, 2013 at 12:34 PM, David Vanderson
david.vander...@gmail.comwrote:
Ah - thank you! I think I finally understand how this works. To make
sure, I query the props like this:
~/apps/racket$ ./pkgs/plt-services/meta/props get drdr:command-line
On Wed, Sep 4, 2013 at 1:55 PM, David Vanderson
david.vander...@gmail.comwrote:
I totally missed pkgs/racket-pkgs/racket-test/tests/run-automated-tests.rkt,
but it looks like DrDr is running that with 'mzc -k _' - doesn't that just
compile it?
Yes, the intention there is to run the tests
It looks to me like most of the tests in
racket/pkgs/racket-pkgs/racket-test/tests/file/* are not being run by
DrDr. I think DrDr is running them with 'raco test _' while the files
mostly need to be run as 'racket _'.
Am I missing something? If not, should I fix the files to be run with
I totally missed
pkgs/racket-pkgs/racket-test/tests/run-automated-tests.rkt, but it looks
like DrDr is running that with 'mzc -k _' - doesn't that just compile it?
There is also a file/main.rkt that runs all the file/ tests, but that
file doesn't show up in DrDr.
I'm more confused now.
5 matches
Mail list logo