Very nice. Thank you Jay. That will be a big help.
On Jul 28, 2015, at 1:22 PM, Jay McCarthy wrote:
> I'm a little later than I expected, but I just added the ability to
> use regexps in test-omit-paths and in a new info.rkt property called
> test-include-paths. The test case [1] shows an exam
I'm a little later than I expected, but I just added the ability to
use regexps in test-omit-paths and in a new info.rkt property called
test-include-paths. The test case [1] shows an example where all files
matching #rx".*include.*" are included, such as the file
`b-include-1.racket-file`. This sh
I think the right thing to do is just make an extension for the
extension and/or the way the file list is built. I'll look into it on
Monday.
Jay
On Thu, Jul 9, 2015 at 6:53 PM, Matthew Butterick wrote:
> Further investigation reveals that the source code of
> `compiler/commands/test` is adaman
Further investigation reveals that the source code of `compiler/commands/test`
is adamant that the only acceptable extensions are 'rkt' and 'scrbl', and that
anything else needs to be handled with 'test-command-line-arguments' [1]. So
this kind of thing will work in an "info.rkt", with each file
`raco test` will automatically test every .rkt and .scrbl file in a
directory. Suppose I make `#lang foo` and thus many of my test files end
with .foo. I would want all .foo files to be automatically tested as well.
Is there a way to use "info.rkt" to tell `raco test` to add file types?
(Should the
5 matches
Mail list logo
