Just in case anyone comes across this, I did get around it. In fig. 2 I was
trying to run (use-fixtures) twice. One with a :once, and one with :each. I
just commented out the :once call and executed manually.
*(use-fixtures :once login-test/test-fixture-shell )*
*(use-fixtures :each login-test/test-fixture-db )*
*(test-fixture-shell nil)*
*;;(use-fixtures :once login-test/test-fixture-shell )*
*(use-fixtures :each login-test/test-fixture-db )*
Tim
On Tue, Sep 28, 2010 at 6:08 PM, Timothy Washington <twash...@gmail.com>wrote:
> Oh that's my mistake in the example code. My actual code does have an (is )
> function. The example code should look like:
>
> (deftest test-code []
> *(is (= 5 5)) *
> )
>
> Tim
>
>
> On Tue, Sep 28, 2010 at 12:29 PM, Kevin Downey <redc...@gmail.com> wrote:
>
>> your test has no (is ...)
>>
>> On Mon, Sep 27, 2010 at 5:16 PM, Timothy Washington <twash...@gmail.com>
>> wrote:
>> > I suppose I've been looking at this code for too long, so I need a 2nd
>> pair
>> > of eyes on it. I'm not getting some 'test.is' code to run. I'm trying
>> to run
>> > the tests as in fig. 1. Suppose the tests are defined in a file called
>> > utests.clj (fig. 2).
>> >
>> > (use 'clojure.test)
>> > (require 'utests)
>> > (run-tests 'utests)
>> > fig. 1 - run attempts
>> >
>> > (ns utests)
>> > (defn test-fixture-1 [test-func]
>> >
>> > (setup-code)
>> > (test-func)
>> > (teardown-code)
>> > )
>> > (use-fixtures :each test-fixture-1)
>> > (deftest test-code []
>> > (= 5 5))
>> > )
>> > fig. 2 - utests.clj
>> >
>> > Ran 0 tests containing 0 assertions.
>> > 0 failures, 0 errors.
>> > {:type :summary, :test 0, :pass 0, :fail 0, :error 0}
>> > fig. 3 - output
>> >
>> >
>> > Q. The thing that I'm missing is...
>> >
>> > Thanks in advance
>> > Tim
>> >
>> > --
>> > 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<clojure%2bunsubscr...@googlegroups.com>
>> > For more options, visit this group at
>> > http://groups.google.com/group/clojure?hl=en
>>
>>
>>
>> --
>> And what is good, Phaedrus,
>> And what is not good—
>> Need we ask anyone to tell us these things?
>>
>> --
>> 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<clojure%2bunsubscr...@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
