Problems with QUnit async tests
Hi,
I am trying to use QUnit test framework for testing/TDD of CouchDB
apps (testing map/reduce, validations, etc).
The basic test case -- testing validations -- could look like this:
http://pastie.textmate.org/764793 (I am testing return value in the
`db.saveDoc()` callbacks.)
The problem is that the results are not reliable: sometimes two
assertions -- `equals()` -- are run, sometimes zero, but never all.
That is, I am getting "Expected 3 assertions, but 2 were run" and
similar failures all the time.
Do you see anything obviously wrong in this example? I've been
following the example in http://docs.jquery.com/QUnit/expect#amount.
Is there some problem with multiple assertion per test? (The test
suite included with QUnit does have multiple assertions per test.)
(For the record, I know of the `asyncTest()` function, I've tried to
be more explicit with the test(), stop(), start() scenario.)
Thanks for any pointers!
Karel
--
I am trying to use QUnit test framework for testing/TDD of CouchDB
apps (testing map/reduce, validations, etc).
The basic test case -- testing validations -- could look like this:
http://pastie.textmate.org/764793 (I am testing return value in the
`db.saveDoc()` callbacks.)
The problem is that the results are not reliable: sometimes two
assertions -- `equals()` -- are run, sometimes zero, but never all.
That is, I am getting "Expected 3 assertions, but 2 were run" and
similar failures all the time.
Do you see anything obviously wrong in this example? I've been
following the example in http://docs.jquery.com/QUnit/expect#amount.
Is there some problem with multiple assertion per test? (The test
suite included with QUnit does have multiple assertions per test.)
(For the record, I know of the `asyncTest()` function, I've tried to
be more explicit with the test(), stop(), start() scenario.)
Thanks for any pointers!
Karel
--
Topic Participants
John Resig