Basically, I ran into the issue this guy reported, but there still hasn't been a fix.
http://yuilibrary.com/forum/viewtopic.php?p=39725
Like the OP mentions, I believe yeti shouldn't call mocha.run(). Maybe it should emit an event that can be listened to. Or from within yeti, mocha starts up based on an event that gets broadcasted by the consumer of yeti.
Basically, I ran into the issue this guy reported, but there still hasn't been a fix.
http://yuilibrary.com/forum/viewtopic.php?p=39725
Like the OP mentions, I believe yeti shouldn't call mocha.run(). Maybe it should emit an event that can be listened to. Or from within yeti, mocha starts up based on an event that gets broadcasted by the consumer of yeti.