Here a example where midje could provide more info.
I have this function :
(defn pr134 [element a-seq]
(and (contains? a-seq element) (nil? element))
)
and I have this test-function :
(ns exercises.core-test
(:use midje.sweet)
(:use [exercises.core]))
(facts "about `pr134`"
(fa
http://jakemccrary.com/blog/2014/06/22/comparing-clojure-testing-libraries-output/
has some good examples. I'm currently using humane-test-output. It's worked
nicely for me.
'(Devin Walters)
> On Nov 1, 2014, at 7:00 PM, Alex Miller wrote:
>
> Additionally, I think it would be helpful to enum
Additionally, I think it would be helpful to enumerate example (failing)
tests and their output by current clojure.test.
On Saturday, November 1, 2014 1:58:32 PM UTC-5, Alex Miller wrote:
>
> It would be great if someone could enumerate more explicitly what "better"
> test output means. What ar
On Nov 1, 2014, at 1:58 PM, Alex Miller wrote:
> It would be great if someone could enumerate more explicitly what "better"
> test output means. What are the specific problems in the current test output
> reporting?
If there's any sort of consensus about test reporting, specifically how
diff
I can say for certain that at a minimum better indentation of data structures
to the console would be a must, a vector with 4+ hash maps in it are currently
unreadable and I have to copy to an editor to indent and analyze.
Beyond that, I can imagine the need for a structural diff that tells me
It would be great if someone could enumerate more explicitly what "better" test
output means. What are the specific problems in the current test output
reporting?
Similar problem list for test runner might be useful.
Discussion here is fine but ultimately needs to land on a design wiki page.
I
That's an excellent idea, currently at least test.check hacks on top of
clojure.test by using macros that emit clojure.test tests.
Beyond that it seems that the #1 wish is better output. I don't think that
ought to be very hard for us to pull off as a community.
On Fri, Oct 31, 2014 at 6:56 P
+1 to something like humane-test-output being part of core library.
There is value for the community to have some foundation library share
across our test frameworks? Something like `test.runners`, to encapsulate
error reporting and organization? Bit crazy, I know, but the idea come
after seein
Would be great if humane-test-output was part of clojure.test. Would make
it easier for beginners to find it.
On Friday, October 31, 2014 11:19:11 PM UTC+8, Eli Naeher wrote:
>
> On Fri, Oct 31, 2014 at 9:52 AM, Ashton Kemerling > wrote:
>
>
>> It's my opinion that these two libraries are lar
I totally agree about pr-str in test.check. Quite often I want to copy and
paste the failure into a repl and play around, but need to re-add missing
quotation marks or quote lists.
> On 31 Oct 2014, at 22:05, Jessica Kerr wrote:
>
> My top wish it more readable output from test.check when run
My top wish it more readable output from test.check when running within
clojure.test
In particular, I want to know the value of each generated parameter at the
first failure, and at the simplest failure. Currently that prints as part
of a map, but if empty-string is generated, that does not sho
On Fri, Oct 31, 2014 at 9:52 AM, Ashton Kemerling wrote:
> It's my opinion that these two libraries are largely complete aside from
> some human interface improvements (quality of output for example), but
> clearly not everyone agrees with me.
>
Hi Ashton,
Check out https://github.com/pjstadig
"I tweeted recently that I thought that Clojure is super testable, and I
was genuinely surprised about the number of people who disagreed with me."
My 2c.
Without explicitly citing those complaints, it will be difficult to conduct
a meaningful debate.
2014-10-31 14:52 GMT+00:00 Ashton Kemerling
I don't want to speak for others, I notified everyone involved on Twitter that
I made this thread so they can voice their own complaints.
On Fri, Oct 31, 2014 at 9:02 AM, László Török wrote:
> "I tweeted recently that I thought that Clojure is super testable, and I
> was genuinely surprised abo
I tweeted recently that I thought that Clojure is super testable, and I was
genuinely surprised about the number of people who disagreed with me.
There's been a lively discussion about what the best testing frameworks in
clojure currently are, and what the built in solutions (clojure.test and
The feedback that comes immediately to mind:
* it sounds like property #3 complects black box vs white box and
specification vs implementation concerns
* it sounds like the feature functions potentially combine the state and
calculation layers in ways that should be internally reused, but also are
On Sat, Apr 6, 2013 at 5:42 PM, Steven Degutis wrote:
> What do you think? What approach would you take in this situation?
I guess I'd turn it around and ask what new problems you think
functional programming introduces for testing - and why do you think
that?
In general, I've found that writing
Forgive me if I completely misunderstood your question. Replies inline.
One way is to use `with-redefs`. This technique would be used at every
> level along the pyramid (except the bottom level which doesn't call
> anything else).
>
>
This would be similar to mocking, correct? If so, what'd be wro
Disclaimer: this isn't strictly about Clojure, more about semi-functional
programming techniques, which Clojure excels at. (Plus I'm using Clojure
for it.)
Lately I've been experimenting with ditching the conventional MVC approach
to writing a web app.
Now controllers are just dead-simple func
ops. thanks
mimmo
On Dec 2, 2012, at 10:15 PM, Michael Klishin
wrote:
> 2012/12/3 Mimmo Cosenza
> I just published the 9th tutorial of the series modern-cljs.
>
> It talks about testing. It uses the CLJS proposed patch as a true sample
> case to work on.
> HIH
>
> The link:
> https://gith
2012/12/3 Mimmo Cosenza
> I just published the 9th tutorial of the series modern-cljs.
>
> It talks about testing. It uses the CLJS proposed patch as a true sample
> case to work on.
> HIH
>
The link:
https://github.com/magomimmo/modern-cljs/blob/master/doc/tutorial-09.md
Thank you!
--
MK
ht
Hi,
I just published the 9th tutorial of the series modern-cljs.
It talks about testing. It uses the CLJS proposed patch as a true sample case
to work on.
HIH
My best
Mimmo
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group
22 matches
Mail list logo
