spadgos / myrtle Goto Github PK

Tests should be able to be executed asynchronously.

Set up the project with the appropriate files for npm integration.

After the test suite has run, Chrome (admittedly version 5 on Ubuntu) does not change the favicon to show the tick or cross. Instead the hourglass remains.

Currently, the this inside a module has functions which a user should never use. Instead, a reduced set of functions should be provided to reduce complexity.

Tyrtle needs to allow users to extend the assert method with custom assertions.

Tests should be able to be skipped - always, as well as conditionally.

this.skip("reason for the skip");
this.skipIf(x === y, "reason for the skip");

Each time a function is mocked, then the API functions are created anew. Instead, many of them could be reused between calls.

The postMessage zero-ms timeout method used internally by Tyrtle (and possibly by other users) is not being modified by fakeTimers. It should.

There should be a convenience method provided so that a function can be instrumented, then a user-defined function can be executed and automatically cleaned up afterwards.

expected:

O.f = function (a, b) { };
alert(O.f.length, 2);

Myrtle.spy(O, 'f');
alert(O.f.length, 2);

actual:

Myrtle.spy(O, 'f');
alert(O.f.length, 0);

It's a bit clunky to have to supply all the options to Myrtle(). There should be only be a single way to spy/stub a method. Spying should be on by default or even non-configurable.

Tyrtle needs to have functions which are executed before and after each test and module. Asynchronous methods should be supported. Designating which of these helpers are asynchronous could be done by counting the arguments, via the function.length property.

// synchronous
this.before(function () { });

// asynchronous
this.before(function (callback) { });