Scott Santucci

It's amazing how easy it is to implement a basic AMD loader for the trivial cases, and how hard it is to implement one that handles circular references, script loading...

It's not so much being cross-browser as working around different bugs* in different versions of IE that's non-trivial. Or at least, that's what I discovered last time I went looking...

This could probably be fixed with array methods now that Mocha 4 supports only newer environments? In any case, it's mostly waiting on #2900, which I need to be able...

@boneskull Disabling timeouts means it will wait until the test completes no matter what (i.e. indefinitely in this case since the test never calls `done`), right? If so, I can...

@boneskull That answers my question, thanks -- the behavior you describe is what I expected. Here's a simpler and clearer demonstration of the issue: test.js: ``` js it("found the test...

So, I ran into this at work the other day, and the weird thing there is my tests actually weren't -- as far as I'm aware -- failing to ever...

Came up with a better way to handle this: If Node would close due to the test having no more actions scheduled and not having called `done` or resolved a...

If Mocha's marking the tests as complete and outputting the summary at the end, then it's not the same issue as this one (which is Mocha closing altogether, no more...

`done()` is success (e.g. `.then(function(){done()})`, although if you're doing this you probably have a case for [returning the promise instead of using `done`](https://mochajs.org/#working-with-promises)); `done()` is failure, so it's trying to...

I've dug into this a bit and determined a few things: - `run` should only be called once total, not once per file. - The documentation needs to be updated...