{"issue":{"user":{"id":444823,"login":"niallsmart","url":"https://api.github.com/users/niallsmart","gravatar_id":"13fc04d54868984f5e9d9ad43075dffe","avatar_url":"https://secure.gravatar.com/avatar/13fc04d54868984f5e9d9ad43075dffe?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"milestone":null,"created_at":"2011-12-20T07:11:00Z","title":"In autorun mode, moduleDone is called without matching moduleStart","updated_at":"2011-12-21T10:55:32Z","labels":[],"state":"open","id":2609976,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"html_url":"https://github.com/jquery/qunit/issues/184","closed_at":null,"number":184,"body":"If `QUnit.config.autorun = true` then Qunit fires a `moduleDone` event after each test completes (as expected) however the `moduleStart` event is only fired when the first test in a module runs.\r\n\r\nLogging `moduleEnd` entries without a corresponding `moduleStart` causes problems with some continuous integration tools (e.g., TeamCity). The attached patch ensures that `moduleStart/moduleDone` always happen in pairs.","url":"https://api.github.com/repos/jquery/qunit/issues/184","comments":1,"assignee":null},"comment":{"user":{"id":52585,"login":"jzaefferer","url":"https://api.github.com/users/jzaefferer","gravatar_id":"a9d4d2558b560b0ef168ced0f6c5198c","avatar_url":"https://secure.gravatar.com/avatar/a9d4d2558b560b0ef168ced0f6c5198c?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"created_at":"2011-12-21T10:55:32Z","updated_at":"2011-12-21T10:55:32Z","id":3232289,"body":"How is a `moduleDone` after each test expected? Shouldn't it also only log `moduleDone` at the end of each module?","url":"https://api.github.com/repos/jquery/qunit/issues/comments/3232289"},"action":"created"}