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
  • 2 hours ago
  • 8 years ago

Installs

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