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
  • 13 years ago
  • 54 minutes ago
  • 13 years ago

Installs

  • Total 1K
  • Win 434
  • Mac 676
  • Linux 200
Jul 1 Jun 30 Jun 29 Jun 28 Jun 27 Jun 26 Jun 25 Jun 24 Jun 23 Jun 22 Jun 21 Jun 20 Jun 19 Jun 18 Jun 17 Jun 16 Jun 15 Jun 14 Jun 13 Jun 12 Jun 11 Jun 10 Jun 9 Jun 8 Jun 7 Jun 6 Jun 5 Jun 4 Jun 3 Jun 2 Jun 1 May 31 May 30 May 29 May 28 May 27 May 26 May 25 May 24 May 23 May 22 May 21 May 20 May 19 May 18
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
Mac 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.