On Nov 9, 2011, at 8:37 AM, AndyK wrote: > Questions about tabular tests... > * can they take a lazy-seq as input?
Do you mean something like having a computation that generates a stream of test inputs and feeds them into a test evaluator? If so, no: all `tabular's` work happens at compile/macroexpansion time. However, the underlying test-execution-and-reporting function is available and takes test descriptions as maps, so you could do something like (map midje.unprocessed/expect* (source-of-test-maps)) > * will the tests be parallelized? (i have anywhere from 10k-20k tests > to run) The code doesn't make any effort to parallelize tests. Tests are normally run as they're encountered at load time. (Unlike clojure.test, the `fact` macro doesn't stash a test-function away for later execution.) A test runner like the above should be parallelizable, though I didn't make any special effort to ensure that. The default reporter just prints results. You'd probably want one that stashes them away in an atom as they come in. There's already a way to swap in different reporters, so that shouldn't be too hard. More discussion should probably happen at http://groups.google.com/group/midje ----- Brian Marick, Artisanal Labrador Now working at http://path11.com Contract programming in Ruby and Clojure Occasional consulting on Agile -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
