I take it that you left some console.log() statements in your code and they're breaking since you don't have Firebug open.
--John On Sun, Jan 3, 2010 at 3:57 PM, Karel Minarik <karel.mina...@gmail.com> wrote: > Just noticed a really strange behaviour: all the tests run in Firefox > when and only when I have Firebug panel open. With Firebug closed/ > suspended, different of tests run on each page load and it never > finishes. Any idea why this is happening? > > Karel > > On Jan 3, 9:41 pm, Karel Minarik <karel.mina...@gmail.com> wrote: >> Hello John, >> >> thank you very much for the clarification. If I stick with the "one >> assertion per async test" everything works really fine. (Though only >> in FF, Safari gives some couch related issues -- no_db_file in setup, >> has still trouble going through the entire suite, etc. Also, Celerity >> does not show the results, while it has been working for a limited >> test suite previously. But I can live with that for the moment.) >> >> Thanks again, >> >> Karel >> >> On Jan 3, 7:00 pm, John Resig <jere...@gmail.com> wrote: >> >> >> >> > The stop() method doesn't really work that way (it would have to >> > behave synchronously for that to be the case). You'll have to do one >> > stop() at the start of the test block and then either do only one >> > async test or just keep a counter of the number of tests that've >> > completed and only run the start() after all of them have returned. >> >> > --John >> >> > On Sun, Jan 3, 2010 at 5:52 AM, Karel Minarik <karel.mina...@gmail.com> >> > wrote: >> > > 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(Iam 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 inhttp://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 >> >> > > -- >> >> > > You received this message because you are subscribed to the Google >> > > Groups "jQuery Development" group. >> > > To post to this group, send email to jquery-...@googlegroups.com. >> > > To unsubscribe from this group, send email to >> > > jquery-dev+unsubscr...@googlegroups.com. >> > > For more options, visit this group >> > > athttp://groups.google.com/group/jquery-dev?hl=en. > > -- > > You received this message because you are subscribed to the Google Groups > "jQuery Development" group. > To post to this group, send email to jquery-...@googlegroups.com. > To unsubscribe from this group, send email to > jquery-dev+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/jquery-dev?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
