lib/generators/teaspoon/install/templates/mocha/spec_helper.coffee in teaspoon-0.7.9 vs lib/generators/teaspoon/install/templates/mocha/spec_helper.coffee in teaspoon-0.8.0

- old
+ new

@@ -2,17 +2,17 @@ # require support/expect # require support/sinon # require support/chai # require support/your-support-file # -# PhantomJS (Teaspoons default driver) doesn't have support for Function.prototype.bind, which has caused confusion. Use -# this polyfill to avoid the confusion. +# PhantomJS (Teaspoons default driver) doesn't have support for Function.prototype.bind, which has caused confusion. +# Use this polyfill to avoid the confusion. #= require support/bind-poly # # Deferring execution -# If you're using CommonJS, RequireJS or some other asynchronous library you can defer execution. Call Teaspoon.execute() -# after everything has been loaded. Simple example of a timeout: +# If you're using CommonJS, RequireJS or some other asynchronous library you can defer execution. Call +# Teaspoon.execute() after everything has been loaded. Simple example of a timeout: # # Teaspoon.defer = true # setTimeout(Teaspoon.execute, 1000) # # Matching files @@ -22,18 +22,18 @@ # # Manifest # If you'd rather require your spec files manually (to control order for instance) you can disable the suite matcher in # the configuration and use this file as a manifest. # +# For more information: http://github.com/modeset/teaspoon +# # Chai -# If you're using Chai, you probably want to initialize your preferred assertion style here. -# For more information see: http://chaijs.com/guide/styles -# Examples: +# If you're using Chai, you'll probably want to initialize your preferred assertion style. You can read more about Chai +# at: http://chaijs.com/guide/styles # -# window.assert = chai.assert -# window.expect = chai.expect -# window.should = chai.should() +# window.assert = chai.assert +# window.expect = chai.expect +# window.should = chai.should() # -# For more information: http://github.com/modeset/teaspoon -# -# You can require javascript files here. A good place to start is by requiring your application.js. +# You can require your own javascript files here. By default this will include everything in application, however you +# may get better load performance if you require the specific files that are being used in the spec that tests them. #= require application