Fix modules with no callbacks

[trentmwillis]

Introduced a bug with #260.

This fixes it and adds a regression test.

[bendemboski]

@trentmwillis @rwjblue I'm seeing a bizarre error that appears to be caused by #260. I run my whole suite, and a few modules towards the end of the suite fail because module is undefined in beforeEach. I put in some logging, and before is not being called for these module. I can see beforeEach() being called for each test (with module=undefined), and after being called, but `before is not getting called.

The tests that are failing are my route and service unit tests -- a couple of route tests pass, then the rest and all the service tests fail, then next is some non-ember-qunit modules that pass.

I'm trying to dig in more to zero in on the cause, but I'm kinda unfamiliar with this code. Any guidance or help would be much appreciated. If either of you have time, you can also hit me up on Ember Community Slack.

ember-cli@2.9.1
ember-cli-qunit@3.1.2
ember-qunit@2.1.2
qunitjs@2.3.1
me@super.duper.confused

[rwjblue]

I put in some logging, and before is not being called for these module.

@bendemboski - Definitely seems unexpected. Can you open up a new issue so we can have somewhere to work with you on tracking it down?

@trentmwillis - Is there anything special about the way before is called in QUnit? Any possible issues with multiple modules using the same name or something like that?

[trentmwillis]

I don't think so. Basically, there is an internal module object that has an array of tests and sub-modules. Whenever a test is run, it checks with the module it is registered with to determine which hooks should fire.

A reproduction would be immensely helpful here as the QUnit hooks are pretty well tested.

[bendemboski]

#268 -- I'll work on getting more info and/or a repro that I can share.

[bendemboski]

Turns out this is a bug in QUnit triggered when the first or last test in a module is skipped. I opened a PR with a fix over there.