lib/generators/teaspoon/install/templates/mocha/spec_helper.js in teaspoon-0.8.0 vs lib/generators/teaspoon/install/templates/mocha/spec_helper.js in teaspoon-0.9.0

- old
+ new

@@ -1,26 +1,31 @@ // Teaspoon includes some support files, but you can use anything from your own support path too. // require support/expect // require support/sinon // require support/chai +// require support/chai-jq-0.0.7 // 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. //= require support/bind-poly // +// 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 +// // 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: // // Teaspoon.defer = true // setTimeout(Teaspoon.execute, 1000) // // Matching files // By default Teaspoon will look for files that match _spec.{js,js.coffee,.coffee}. Add a filename_spec.js file in your // spec path and it'll be included in the default suite automatically. If you want to customize suites, check out the -// configuration in config/initializers/teaspoon.rb +// configuration in teaspoon_env.rb // // 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. // @@ -31,9 +36,5 @@ // at: http://chaijs.com/guide/styles // // window.assert = chai.assert; // window.expect = chai.expect; // window.should = chai.should(); -// -// 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