ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Mocha Runner

by matthiasg ST2

Simple plugin which automatically runs mocha.

Details

  • 2012.12.04.10.51.07
  • github.​com
  • github.​com
  • 7 years ago
  • 1 hour ago
  • 7 years ago

Installs

  • Total 1K
  • Win 433
  • OS X 676
  • Linux 200
Oct 18 Oct 17 Oct 16 Oct 15 Oct 14 Oct 13 Oct 12 Oct 11 Oct 10 Oct 9 Oct 8 Oct 7 Oct 6 Oct 5 Oct 4 Oct 3 Oct 2 Oct 1 Sep 30 Sep 29 Sep 28 Sep 27 Sep 26 Sep 25 Sep 24 Sep 23 Sep 22 Sep 21 Sep 20 Sep 19 Sep 18 Sep 17 Sep 16 Sep 15 Sep 14 Sep 13 Sep 12 Sep 11 Sep 10 Sep 9 Sep 8 Sep 7 Sep 6 Sep 5 Sep 4
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
OS X 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

sublime-mocha-runner

NOTE: node.js under windows has a bug where it does not always flush console.log output before exiting. This is most prominent when redirecting to another file or process (which is what mocha-runner does). Therefore the output sometimes screws up especially it is the reason the stack trace does not appear on errors. Ticket: https://github.com/joyent/node/issues/3584

Whenever a file is saved it searches the directory tree upwards for a test folder. When one is found it runs mocha.

The runner writes success and a timestamp into the status bar of the currently saved view. When mocha detects failures it writes all failed tests TAP style to a new output view.

There are no settings it disable it yet and ALWAYS runs mocha whenever a folder named test is detected. This should not cause any problems though.

NOTE: The program under test should not output anything to the console. This would screw up the TAP output required for parsing and most likely also the tests.