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
Hi all,
I just published the 15th tutorial of the series modern-cljs.
https://github.com/magomimmo/modern-cljs
After having implemented the server side validators, it introduces unit testing.
HIH
My best regards
Mimmo
--
--
You received this message because you are subscribed to the Google
If you are coming from Ruby, there is speclj which has an RSpec feel.
https://github.com/slagyr/speclj
On Tue, Jan 8, 2013 at 1:57 PM, Sean Corfield wrote:
> On Mon, Jan 7, 2013 at 11:50 PM, Eric MacAdie wrote:
> > Is there a common unit testing framework for Clojure? I did some
&
On Mon, Jan 7, 2013 at 11:50 PM, Eric MacAdie wrote:
> Is there a common unit testing framework for Clojure? I did some googling,
> put all the results were a couple of years old.
As others have noted separately, Clojure has clojure.test built-in
which is fairly straightforward assertion
There's also Midje: https://github.com/marick/Midje
On Tue, Jan 8, 2013 at 12:54 AM, keeds wrote:
> Expectations is a good framework.
>
> https://github.com/jaycfields/expectations
>
>
> On Tuesday, January 8, 2013 7:50:05 AM UTC, Eric MacAdie wrote:
>>
>
Expectations is a good framework.
https://github.com/jaycfields/expectations
On Tuesday, January 8, 2013 7:50:05 AM UTC, Eric MacAdie wrote:
>
> Is there a common unit testing framework for Clojure? I did some googling,
> put all the results were a couple of years old.
>
>
Hi,
Am Dienstag, 8. Januar 2013 08:50:05 UTC+1 schrieb Eric MacAdie:
>
> Is there a common unit testing framework for Clojure? I did some googling,
> put all the results were a couple of years old.
>
>
clojure.test ships with clojure proper. And midje is also very popular.
Kind
Is there a common unit testing framework for Clojure? I did some googling,
put all the results were a couple of years old.
- Eric MacAdie
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@google
On Jan 12, 8:39 am, Eric Thorsen wrote:
> Anyone have any recommendation/experience for a unit testing library
> for testing swing components?
>
> Thanks!
> Eric
We've used FEST [1] in school. It worked, but testing GUI code is
horrible.
[1] http://fest.easytesting.org/wik
I saw this.
I'll give it a try.
Thanks,
Eric
On Jan 12, 10:06 am, Roger Gilliar wrote:
> Hi,
>
> we use Jemmy for this purpose (https://jemmy.dev.java.net/)
>
> Regards
> Roger
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this grou
Eric Thorsen napisał(a):
> Anyone have any recommendation/experience for a unit testing library
> for testing swing components?
For simple module testing I use marathon [1] and for this purpose can
recommend it.
Test scripts can be written in Python not Clojure, though. ;)
[1
Hi,
we use Jemmy for this purpose (https://jemmy.dev.java.net/)
Regards
Roger
--
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 b
and I manually test that each one calls the expected
routine.
Manual testing seems to be required. I would use the opportunity to
review the workflow of your application, to see that it does what you
want.
Sean
On Jan 12, 9:39 am, Eric Thorsen wrote:
> Anyone have any recommendation/experience fo
Anyone have any recommendation/experience for a unit testing library
for testing swing components?
Thanks!
Eric
--
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 post
>> 2) put the unit tests in a separate file, in the same namespace
This works for me, but since it won't work with the normal use/require
idiom, I would like to see a standard convention evolve to make it
easy to read other people's code.
Stu
--~--~-~--~~~---~--~
Stuart Sierra a écrit :
> Stu's suggestion of with-ns would also work. But you don't even need
> with-ns. You can refer a private function into the local namespace
> like this:
>
> (def private-function (ns-resolve 'other-namespace 'private-function))
>
And don't forget the good old @#'other
(when (:private (meta var))
(intern *ns* symbol var
This is slightly evil, and I would never recommend it for any purpose
except unit testing, but there it is.
-Stuart Sierra
On Wed, Jun 3, 2009 at 12:36 AM, Stuart Halloway
wrote:
> Hi Allen,
>
> You c
Well, of course this is a classic situation in OO, if you think about it.
Googling around may shed some interesting light on the subject. Essentially,
the question is: are you sure that's what you want to do? Why not
concentrate your unit tests on the public interface in such a way that the
private
Hi everyone,
I agree with Stuart, this would be very helpfull.
Thank you,
Stephan
On Jun 3, 12:36 am, Stuart Halloway wrote:
> Hi Allen,
>
> You could write a function that uses the clojure.contrib.with-ns/with-
> ns macro to dip into the namespace being tested and return the private
> func
Hi Allen,
You could write a function that uses the clojure.contrib.with-ns/with-
ns macro to dip into the namespace being tested and return the private
function, assigning it to a local name in the test namespace.
I need this too, and have been meaning to ping the other Stuart about
either
I have a namespace with some public functions, and some private
functions. I would like to write unit tests for the functions, and put
them in a separate file from the main name space. I would also like to
have an (ns) declaration in my tests file, because the tests require
several libraries. Of c
Hi folks,
A while ago I started writing a unit testing library called Fact that
was a cross between Haskell's QuickCheck, and Ruby's RSpec. I've done
a lot of work with it, and some people might conceivably be interested
in how I got on with it, so this post is to chart what
Thanks to everyone who replied. After looking at the examples & a
night's sleep, this makes sense.
On Mar 18, 12:38 pm, Stuart Sierra
wrote:
> On Mar 17, 6:06 pm, Sean wrote:
>
> > I'm writing a macro library for myself, and I'm thinking about
> > publishing it. Before I do so, I'd like to
On Mar 17, 6:06 pm, Sean wrote:
> I'm writing a macro library for myself, and I'm thinking about
> publishing it. Before I do so, I'd like to write & run some unit
> tests for it. I was hoping the crowd could chime in on how they test
> macros. Any links & examples would be great. Thanks!
On Tue, Mar 17, 2009 at 5:06 PM, Sean wrote:
>
> Hey everyone,
> I'm writing a macro library for myself, and I'm thinking about
> publishing it. Before I do so, I'd like to write & run some unit
> tests for it. I was hoping the crowd could chime in on how they test
> macros. Any links & ex
Hey everyone,
I'm writing a macro library for myself, and I'm thinking about
publishing it. Before I do so, I'd like to write & run some unit
tests for it. I was hoping the crowd could chime in on how they test
macros. Any links & examples would be great. Thanks!
--~--~-~--~--
Hi folks,
I've put together a unit testing library that borrows ideas from
Ruby's RSpec and Haskell's Quickcheck. In Fact, you define a series of
facts that are verified by predicates. These predicates are tested
many times with sequences of data.
A "fact" takes the
36 matches
Mail list logo
