> On twitter, @InderjitGill pointed to this thread that may be helpful:

> https://groups.google.com/forum/?fromgroups=#!topic/yeoman-dev/5TLE8A...

> I have not used mocha though so I do not quite follow it.

> On Tue, Oct 2, 2012 at 12:06 PM, Erwin Poeze <erwin...@gmail.com<javascript:>>
> wrote:
> > I'm trying to figure out if mocha as some sort of stop/start
> functionality,
> > like qunit has for example. I ran into an old request for a deferred
> > execution (https://github.com/visionmedia/mocha/issues/362).

> > The browser version of moncha does seem to have such an option,
> mocha.run(),
> > but I can get the browser version running in node.

> > On Tuesday, October 2, 2012 7:41:35 PM UTC+2, James Burke wrote:

> >> Does Mocha have a "start" method? Maybe tell it not to autostart, and
> >> only start inside the require callback? QUnit has something like that.

> >> The "require always async" is to get more consistent behavior, so
> >> making that call synchronous is not suggested. I would like to sort
> >> out a solution that does not require it to be synchronous, as it may
> >> lead to subtle bugs, particularly after a build (the kind of bug that
> >> triggered this change in 2.1).

> >> You can force sync by overriding requirejs.nextTick to just call the
> >> fn passed to it. But this is not recommended, let's try to sort out
> >> how to use Mocha correctly for these async cases.

> >> James

> >> On Mon, Oct 1, 2012 at 11:02 PM, Erwin Poeze <erwin...@gmail.com>
> wrote:
> >> > Ok, I see. Mocha doesn't seem to have a 'wait' state. Can't the top
> >> > level
> >> > requirejs by set to sync?

> >> > On Monday, October 1, 2012 11:07:48 PM UTC+2, James Burke wrote:

> >> >> My guess is that now requirejs([], function (){}) calls always call
> >> >> the callback asynchronously. Is there a "wait" state you can put
> mocha
> >> >> in before doing the requirejs([]) call, and then resume it once the
> >> >> callback is called?

> >> >> James

> >> >> On Mon, Oct 1, 2012 at 2:51 AM, Erwin Poeze <erwin...@gmail.com>
> wrote:
> >> >> > Hi,

> >> >> > I tried to use dev2.1 because it seems it has a bug is solved that
> I
> >> >> > encountered too. When I run existing test cases with mocha using
> the
> >> >> > dev2.1
> >> >> > r.js, mocha seems to skip all the test (0 tests completed). When a
> >> >> > rebase
> >> >> > r.js to master and create the r.js again, the mocha tests run ok.

> >> >> > The most simple testcase I could create is (not testing anything,
> >> >> > just
> >> >> > echoing to console):

> >> >> > var requirejs = require('../r.js');
> >> >> > //var requirejs = require('requirejs');

> >> >> > requirejs.config({
> >> >> >   baseUrl: __dirname+'/..',
> >> >> >   nodeRequire: require
> >> >> > });

> >> >> > requirejs([
> >> >> >   'lib/schemas/Layout'
> >> >> > ],
> >> >> > function(
> >> >> >   LayoutSchema
> >> >> > ) {
> >> >> >   describe('Test', function() {
> >> >> >     describe('should show', function() {
> >> >> >       it('something', function(done) {
> >> >> >         console.log('layout')
> >> >> >         done();
> >> >> >       });
> >> >> >     });
> >> >> >   });
> >> >> > });

> >> >> > Does anyone have similar experiences?

> >> >> > Thanks.