It's also interesting to note that I most often write my clojure.test code
thusly:
(is (= (some-function some-val)
42))
Which reads pretty much the same way, but without (many) macros.
Technically `is` is a deep walking macro, but that's more about error
reporting than DSLs.
Timothy
On
Timothy Baldridge wrote:
This is a good example of a DSL, and it falls under the criticisms I
level at most DSLs, mainly they aren't Clojure. If we dive into
I note that Midje once had an intermediate “semi-sweet” functional
interface that the `fact` macro expanded into. (It was most similar
Based on the way I've been using midje and the way I use clojure.test, I
really appreciate the middle path fudje has chosen. I don't think the DSL
underneath has caused any confusion, and the team I'm working with is
composed of seasoned Clojure programmers who have never used midje before.
Anecdot
Thanks for taking the time to reply.
Yes, let me clarify what I mean by DSL. Let's say I in my code somewhere
say:
(println (just 42))
What is printed in my repl is an instance of the JustChecker type. Calling
(just ...) doesn't do anything on its own, it constructs am Abstract Syntax
Tree (AST)
Hi again Timothy,
I just got what you meant! by DSL you mean the 'free-floating' checkers
right? You mean that you'd prefer to see the checkers as `assert-expr`
extensions so they are recognizable by `is` yes? I'm not entirely
opposed to that but that would mean one `is` per assertion, which s
Hi Timothy,
Many thanks for taking the time to look into fudje...It is nowhere near
as mature as midje but I find it pretty neat and a pleasure to work with
so far (apart from the 'multimock' workaround perhaps). Also, many
thanks for your feedback...It seems you have misunderstood the purpose
So a bit of constructive feedback on Fudje, firstly, I like that it's
pretty simple, I can take bits I want and leave bits I don't, so good work
on that.
But I do have a issue with the sweet.clj syntax, and I think it's best
exemplified by the code found in the intro:
(testing "arg-checker in mo
Hi Brian,
Thanks for your kind words and, of course, for midje...I've been using
it for years!
About the AOT issues, i was mainly referring to this:
https://github.com/marick/Midje/issues/274
In addition, where i work we have to package our 'harness-testing'
module separately and not AOT it.
dimitris wrote:
This is a small testing library inspired by midje.
For what it's worth, I (author of Midje) think this is wonderful.
You might consider emphasizing that you have similar checkers, as I
think that's one of Midje's strong points. I've been recently
incorporating https://github.
Hi everyone,
This is a small testing library inspired by midje. Before you start
pulling your hair, about why do we need yet another unit-testing
library, please consider reading the README and/or intro.md.
https://github.com/jimpil/fudje
TL/DR;
Midje comes with some very cool features but
10 matches
Mail list logo
