Laurent, as far as I know, the blog entries are still up to date. I've only
documented the stable features of expectations, thus they shouldn't have
changed since the blog entires were written. That said, please do let me know
if anything is incorrect.
Sean, JUnit integration should be as simple as creating your own class that
looks like this one:
jfields$ cat src/proj/test/expectations/AllExpectations.java
package expectations;
import expectations.junit.ExpectationsTestRunner;
import org.junit.runner.RunWith;
@RunWith(ExpectationsTestRunner.class)
public class AllExpectations implements ExpectationsTestRunner.TestSource{
public String testPath() {
return "test";
}
}
I'm returning a path that's relative (from testPath), but it should work with
an absolute path as well - if that's what you want. Then you just run the
AllExpectations.java class the same as you would for any JUnit test class.
Cheers, Jay
On Aug 7, 2012, at 10:47 PM, Laurent PETIT wrote:
> Hello Jay,
>
> thanks for this really great livrary.
>
> I can see that there's a thorough analysis of the framework in a blog series,
> but which may or may not be up to date. At least, it seems a little bit
> "dated" (in software duration time scales), but maybe it's still accurate.
> Maybe updates on the blogs may help the newcomer understand if it's worth
> reading now in August 2012 ?
>
> As for IDE integration via JUnit bridge, I'll try to test it and report back
> when I return from holidays.
>
> Cheers,
>
> --
> Laurent
>
> 2012/8/7 Jay Fields <j...@jayfields.com>
> Hello all,
>
> expectations (github.com/jaycfields/expectations) is an opinionated testing
> framework that is available for anyone to use. I've been using it to test my
> production code for almost 2 years now, and it's used by various teams at DRW
> (http://drw.com) to test their production code as well.
>
> more info is on the readme at github.com/jaycfields/expectations
>
> If you want to use expectations you probably want to check out
> - auto-execpt
> - lein-expectations
> - expectations-mode
>
> and, if you're in an env where you're using an IDE, you'll probably want to
> check out the JUnit integration. It runs very well in IntelliJ (run failed
> tests doesn't work, everything else does afaik).
>
> Cheers, Jay
>
> On Aug 7, 2012, at 12:14 AM, Laurent PETIT wrote:
>
>> Wow Expectations wasn't in my radar, thanks for helping me fix this, since
>> it looks like a really useful and featureful test library.
>>
>> I love the way it clearly has a path to JUnit integration which should
>> really help leverage existing IDEs possibilities in this area.
>>
>> Makes me think again on working on a better automated tests story for
>> Counterclockwise users ...
>>
>> 2012/8/7 Laurent PETIT <laurent.pe...@gmail.com>
>> Thanks,
>>
>> sorry for the short email, it was sent from smartphone
>>
>>
>> 2012/8/6 Sean Corfield <seancorfi...@gmail.com>
>> On Mon, Aug 6, 2012 at 12:01 PM, Laurent PETIT <laurent.pe...@gmail.com>
>> wrote:
>> > Links ?
>>
>> https://clojars.org/lein-expectations
>> https://github.com/gar3thjon3s/lein-expectations
>>
>> > Le 6 août 2012 à 20:43, Sean Corfield <seancorfi...@gmail.com> a écrit :
>> >> lein-expectations - the plugin for running Jay Fields' awesome
>> >> Expectations testing library - has been updated for Leiningen 2.0.
>> >>
>> >> If you are using Leiningen 1.x, continue to use lein-expectations 0.0.5.
>> >>
>> >> If you are on Leiningen 2.x, you should use lein-expectations 0.0.7 so
>> >> that exit on test failure is handled correctly.
>> >>
>> >> 0.0.6 added a partial fix for exit codes in Leiningen 2.0 but it
>> >> didn't work properly with "with-profile". After discussions with Phil
>> >> H about exit status codes, the logic was changed / simplified for the
>> >> 0.0.7 release.
>>
>> --
>> 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
>>
>>
>>
>> --
>> 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
>
>
> --
> 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
>
>
> --
> 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
--
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
