cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Mocny <>
Subject Re: [mobile-spec] consistency and reliability
Date Mon, 03 Nov 2014 21:09:17 GMT
I thought tap was just a format for reporting test results?  I think the
problem is that we have some poorly written tests and the framework is not
recovering well.  Any reporting format is orthogonal (unless perhaps the
bug is specific to the jasmine-html reporter, but I'm not sure there is any
evidence of that).

That said, writing well behaving async tests can be difficult, so I would
hope any test framework would do better to defend against that.  Perhaps
tape is better.  During the big test migration I evaluated mocha (BDD
style) as a replacement for jasmine-2.0 since the test definition format is
really similar, but it had a silly limitation that made porting some tests
difficult: no support for async describe() blocks, and could not nest it()
blocks as a workaround.  I don't recall the specific plugin(s) which had an
issue with this.


On Mon, Nov 3, 2014 at 3:05 PM, Marcel Kinard <> wrote:

> I haven't seen tap/tape until Brian mentioned it here. From a quick read,
> it looks like a port of the tests from Jasmine to tape will be required on
> the runner side. Then we can use whatever reporting we want that can
> consume tap. So if I understand it correctly, the existing tests aren't
> throwaway, but getting off Jasmine certainly won't be free. Assuming that
> tape is less brittle and not substantially less functional that Jasmine,
> could be a net win. Doing the port looks like it will take a fair amount of
> crank-turning.
> On Oct 30, 2014, at 8:09 PM, Brian LeRoux <> wrote:
> > Nope.
> >
> > On Thu, Oct 30, 2014, 5:04 PM Jesse <> wrote:
> >
> >> I would much rather we fix things, than continually rewrite + discard,
> >> which seems to be the norm these days.
> >> tape/tap would require us to throw away thousands of jasmine2 based
> tests
> >> wouldn't it?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message