Coverage remained the same when pulling f0c0199 on geekdave:feature-before-after-context into c754381 on beatfactor:master.

Adding some unit tests for these changes would help keep these features in future versions.

👍 for tests..

@avaly @beatfactor : I couldn't find any tests that were verifying the existing global before / after functions (there is a sampleWithBeforeAndAfter.js test, but it uses the local versions of these functions, not the global ones), so it was not immediately obvious how to demonstrate this bug with a test.

I'll see if I can figure out how to add those tests though. In the meantime, any pointers would be appreciated!

There are no tests for global before / after unfortunately. However I'm a bit reluctant on giving these methods the same context as the test runner. I think they should have the same context as the globals module where they are defined.

You can define environment aware globals which would likely solve your problem, so something like:

module.exports = {
  remote : true,
  'local' : {
    remote: false
  },

  before : function() {
    if (!this.remote) {
       // do something local
    }
  }
};

or even:

module.exports = {
  'local' : {
    before : function() {
      // do something local
    }
  }
};

The second approach works already, the first one needs the context change.

Thanks @beatfactor - Will try implementing as you suggested. Closing this PR.