On Sun, Dec 7, 2008 at 10:51 AM, Stuart Sierra
wrote:
>
> As of clojure-contrib SVN 283, there's a new clojure.contrib.test-is.
> This is a pretty major rewrite of the library. I've tried to
> streamline the code and make it easier to plug in custom reporting and
> assertion functions. Unfortuna
On Dec 9, 2:56 am, Dan Larkin <[EMAIL PROTECTED]> wrote:
> Just one bone to pick, though. The "are" macro doesn't work so well
> if I want to test a custom assert-expr function that only deals with a
> single expression.
Yeah, "are" isn't right. It's going to change, either by specifying
th
Hey this looks great!
On Dec 7, 2008, at 10:51 AM, Stuart Sierra wrote:
>
> Hi folks,
...
>
> 2. "each=" and "all-true" are gone, replaced by the new macro "are",
> which works with any predicate:
>(are =
> 2 (+ 1 1)
> 4 (+ 2 2))
>
Just one bone to pick, though. The "are" macro d
RSpec's contexts are for grouping tests—or defining specifications—for
a Ruby class:
describe Account do
it "should be able to withdraw money and reflect it in its balance"
do
...
end
end
...creates a test basically called "Account should be able to withdraw
money and reflect it in its b
I agree that the ability to nest tests is important, but I'm not sure
encoding the nesting information in the test name is necessarily the
right way to go. Perhaps an intermediate step would be to define a
"test container" that, when executed, runs all the tests it contains.
With that foundation,
On Mon, Dec 8, 2008 at 9:24 PM, Stuart Sierra
<[EMAIL PROTECTED]> wrote:
>
> On Dec 8, 3:53 pm, "J. McConnell" <[EMAIL PROTECTED]> wrote:
>> Great! Will the planned thrown-with-msg? support regex matching? I
>> used something like that in clojure.contrib.test-clojure.evaluation,
>> which was prett
On Dec 8, 3:53 pm, "J. McConnell" <[EMAIL PROTECTED]> wrote:
> Great! Will the planned thrown-with-msg? support regex matching? I
> used something like that in clojure.contrib.test-clojure.evaluation,
> which was pretty handy.
Yes, that's where I got the idea.
-Stuart Sierra
--~--~-~--~-
On Dec 8, 5:06 pm, "Frantisek Sodomka" <[EMAIL PROTECTED]>
wrote:
> I just wonder - how do you define "all-true" using "are"? Since "are"
> always makes pairs for predicate, it might not be possible.
Hi Frantisek,
The short answer is, you don't. :) Just use "is" for now. I'll
consider making
> 2. "each=" and "all-true" are gone, replaced by the new macro "are",
> which works with any predicate:
> (are =
> 2 (+ 1 1)
> 4 (+ 2 2))
>
> -Stuart Sierra
Hello and thanks for additions!
Happy to see additions and work done on tests :-)
I just wonder - how do you define "all-
On Sun, Dec 7, 2008 at 10:51 AM, Stuart Sierra
<[EMAIL PROTECTED]> wrote:
>
> 1. More "is" predicates, including regular expressions and "thrown-
> with-msg?"
Great! Will the planned thrown-with-msg? support regex matching? I
used something like that in clojure.contrib.test-clojure.evaluation,
wh
On Dec 7, 8:51 am, Stuart Sierra <[EMAIL PROTECTED]> wrote:
> 2. Nested test contexts, as in RSpec and some other testing
> frameworks.
>
I would wholeheartedly love if tests could be nested. Even if it was
as simple as appending a phrase to each nested test:
(defcontext "str-starts-with?"
(d
On Dec 7, 2:49 pm, Allen Rohner <[EMAIL PROTECTED]> wrote:
> An acceptable alternative would be to have a way to run all the tests
> in a namespace and all 'children' of a namespace. Then I could create
> a namespace like "test.functional.db.foo" "test.functional.db.bar" and
> then say "(run-tests
On Dec 7, 2:51 pm, Allen Rohner <[EMAIL PROTECTED]> wrote:
> One other feature idea: I'd like the ability to run individual tests.
> Once I've discovered a unit test failure, I want to be able to run the
> test by itself without the noise from other tests.
You can do that now with test-var, which
One other feature idea: I'd like the ability to run individual tests.
Once I've discovered a unit test failure, I want to be able to run the
test by itself without the noise from other tests.
Allen
--~--~-~--~~~---~--~~
You received this message because you are sub
> In the mean time; I'm happy to hear about what you think, and
> any other improvements I could make to the library. Some things I
> have in mind for the next version:
>
> 3. Adding test metadata to vars that are already defined elsewhere.
>
I had a related idea the other night. I commonly like
Hi folks,
As of clojure-contrib SVN 283, there's a new clojure.contrib.test-is.
This is a pretty major rewrite of the library. I've tried to
streamline the code and make it easier to plug in custom reporting and
assertion functions. Unfortunately, this introduces several breaking
changes:
1. "t
16 matches
Mail list logo
