fix teaspoon errors.

1 files changed, 0 insertions, 64 deletions

diff --git a/config/initializers/teaspoon.rb b/config/initializers/teaspoon.rb
deleted file mode 100644
index cf26690d..00000000
--- a/config/initializers/teaspoon.rb
+++ /dev/null
@@ -1,64 +0,0 @@
-Teaspoon.setup do |config|
-
-  # This determines where the Teaspoon routes will be mounted. Changing this to "/jasmine" would allow you to browse to
-  # http://localhost:3000/jasmine to run your specs.
-  config.mount_at = "/teaspoon"
-
-  # This defaults to Rails.root if left nil. If you're testing an engine using a dummy application it can be useful to
-  # set this to your engines root.. E.g. `Teaspoon::Engine.root`
-  config.root = nil
-
-  # These paths are appended to the Rails assets paths (relative to config.root), and by default is an array that you
-  # can replace or add to.
-  config.asset_paths = ["spec/javascripts", "spec/javascripts/stylesheets"]
-
-  # Fixtures are rendered through a standard controller. This means you can use things like HAML or RABL/JBuilder, etc.
-  # to generate fixtures within this path.
-  config.fixture_path = "spec/javascripts/fixtures"
-
-  # You can modify the default suite configuration and create new suites here. Suites can be isolated from one another.
-  # When defining a suite you can provide a name and a block. If the name is left blank, :default is assumed. You can
-  # omit various directives and the defaults will be used.
-  #
-  # To run a specific suite
-  #   - in the browser: http://localhost/teaspoon/[suite_name]
-  #   - from the command line: rake teaspoon suite=[suite_name]
-  config.suite do |suite|
-
-    # You can specify a file matcher and all matching files will be loaded when the suite is run. It's important that
-    # these files are serve-able from sprockets.
-    #
-    # Note: Can also be set to nil.
-    suite.matcher = "{spec/javascripts,app/assets}/**/*_spec.{js,js.coffee,coffee}"
-
-    # Each suite can load a different helper, which can in turn require additional files. This file is loaded before
-    # your specs are loaded, and can be used as a manifest.
-    suite.helper = "spec_helper"
-
-    # These are the core Teaspoon javascripts. It's strongly encouraged to include only the base files here. You can
-    # require other support libraries in your spec helper, which allows you to change them without having to restart the
-    # server.
-    #
-    # Available frameworks: teaspoon-jasmine, teaspoon-mocha, teaspoon-qunit
-    #
-    # Note: To use the CoffeeScript source files use `"teaspoon/jasmine"` etc.
-    suite.javascripts = ["teaspoon-jasmine"]
-
-    # If you want to change how Teaspoon looks, or include your own stylesheets you can do that here. The default is the
-    # stylesheet for the HTML reporter.
-    suite.stylesheets = ["teaspoon"]
-
-    # When running coverage reports, you probably want to exclude libraries that you're not testing.
-    # Accepts an array of filenames or regular expressions. The default is to exclude assets from vendors or gems.
-    suite.no_coverage = [%r{/lib/ruby/gems/}, %r{/vendor/assets/}, %r{/support/}, %r{/(.+)_helper.}]
-    # suite.no_coverage << "jquery.min.js" # excludes jquery from coverage reports
-
-  end
-
-  # Example suite. Since we're just filtering to files already within the root spec/javascripts, these files will also
-  # be run in the default suite -- but can be focused into a more specific suite.
-  #config.suite :targeted do |suite|
-  #  suite.matcher = "spec/javascripts/targeted/*_spec.{js,js.coffee,coffee}"
-  #end
-
-end if defined?(Teaspoon) && Teaspoon.respond_to?(:setup) # let Teaspoon be undefined outside of development/test/asset groups