teaspoon 0.9.1 → 1.0.0

data/app/assets/javascripts/teaspoon/qunit/reporters/console.coffee

@@ -1,25 +0,0 @@
-class Teaspoon.Reporters.Console extends Teaspoon.Reporters.Console
-
-  constructor: (env) ->
-    super
-    env.log(@reportSpecResults)
-    env.testDone(@reportSpecResults)
-    env.done(@reportRunnerResults)
-    @reportRunnerStarting()
-
-
-  reportRunnerStarting: ->
-    @currentAssertions = []
-    @log
-      type:  "runner"
-      total: null
-      start: JSON.parse(JSON.stringify(@start))
-
-
-  reportSpecResults: (result) =>
-    unless typeof(result.total) == "number"
-      @currentAssertions.push(result)
-      return
-    result.assertions = @currentAssertions
-    @currentAssertions = []
-    super(result)

data/app/assets/javascripts/teaspoon/qunit/reporters/html.coffee

@@ -1,80 +0,0 @@
-class Teaspoon.Reporters.HTML extends Teaspoon.Reporters.HTML
-
-  constructor: (env) ->
-    super
-    env.log(@reportSpecResults)
-    env.testDone(@reportSpecResults)
-    env.done(@reportRunnerResults)
-    @currentAssertions = []
-    @reportRunnerStarting()
-
-
-  reportRunnerStarting: ->
-    @total.exist = null
-    @setText("stats-duration", "...")
-
-
-  reportSpecResults: (spec) =>
-    unless typeof(spec.total) == "number"
-      @currentAssertions.push(spec)
-      return
-    spec.assertions = @currentAssertions
-    @currentAssertions = []
-    @reportSpecStarting(spec)
-    super(spec)
-
-
-  reportRunnerResults: (result) =>
-    @total.exist = @total.run = result.total
-    super
-
-
-  readConfig: ->
-    super
-    QUnit.config.notrycatch = @config["use-catch"]
-
-
-  envInfo: ->
-    "qunit #{_qunit_version || "[unknown version]"}"
-
-
-
-class Teaspoon.Reporters.HTML.SpecView extends Teaspoon.Reporters.HTML.SpecView
-
-  buildErrors: ->
-    div = @createEl("div")
-    html = ""
-    for error in @spec.errors()
-      html += """<strong>#{error.message}</strong><br/>#{@htmlSafe(error.stack || "Stack trace unavailable")}<br/>"""
-    div.innerHTML = html
-    @append(div)
-
-
-  buildParent: ->
-    parent = @spec.parent
-    return @reporter unless parent
-    if @views.suites[parent.description]
-      @views.suites[parent.description]
-    else
-      view = new Teaspoon.Reporters.HTML.SuiteView(parent, @reporter)
-      @views.suites[parent.description] = view
-
-
-
-class Teaspoon.Reporters.HTML.FailureView extends Teaspoon.Reporters.HTML.FailureView
-
-  build: ->
-    super("spec")
-    html = """<h1 class="teaspoon-clearfix"><a href="#{@spec.link}">#{@htmlSafe(@spec.fullDescription)}</a></h1>"""
-    for error in @spec.errors()
-      html += """<div><strong>#{error.message}</strong><br/>#{@htmlSafe(error.stack || "Stack trace unavailable")}</div>"""
-    @el.innerHTML = html
-
-
-
-class Teaspoon.Reporters.HTML.SuiteView extends Teaspoon.Reporters.HTML.SuiteView
-
-  constructor: (@suite, @reporter) ->
-    @views = @reporter.views
-    @views.suites[@suite.description] = @
-    @build()

data/lib/generators/teaspoon/install/templates/jasmine/env.rb

@@ -1,11 +0,0 @@
-# Set RAILS_ROOT and load the environment if it's not already loaded.
-unless defined?(Rails)
-  ENV["RAILS_ROOT"] = File.expand_path("../../", __FILE__)
-  require File.expand_path("../../config/environment", __FILE__)
-end
-
-Teaspoon.configure do |config|
-  config.suite do |suite|
-    suite.use_framework :jasmine, "1.3.1"
-  end
-end

data/lib/generators/teaspoon/install/templates/jasmine/spec_helper.coffee

@@ -1,31 +0,0 @@
-# Teaspoon includes some support files, but you can use anything from your own support path too.
-# require support/jasmine-jquery-1.7.0
-# require support/jasmine-jquery-2.0.0
-# require support/sinon
-# 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 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.
-#
-# For more information: http://github.com/modeset/teaspoon

data/lib/generators/teaspoon/install/templates/jasmine/spec_helper.js

@@ -1,31 +0,0 @@
-// Teaspoon includes some support files, but you can use anything from your own support path too.
-// require support/jasmine-jquery-1.7.0
-// require support/jasmine-jquery-2.0.0
-// require support/sinon
-// 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 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.
-//
-// For more information: http://github.com/modeset/teaspoon

data/lib/generators/teaspoon/install/templates/mocha/env.rb

@@ -1,11 +0,0 @@
-# Set RAILS_ROOT and load the environment if it's not already loaded.
-unless defined?(Rails)
-  ENV["RAILS_ROOT"] = File.expand_path("../../", __FILE__)
-  require File.expand_path("../../config/environment", __FILE__)
-end
-
-Teaspoon.configure do |config|
-  config.suite do |suite|
-    suite.use_framework :mocha
-  end
-end

data/lib/generators/teaspoon/install/templates/mocha/env_comments.rb.tt

@@ -1,187 +0,0 @@
-# Set RAILS_ROOT and load the environment if it's not already loaded.
-unless defined?(Rails)
-  ENV["RAILS_ROOT"] = File.expand_path("../../", __FILE__)
-  require File.expand_path("../../config/environment", __FILE__)
-end
-
-Teaspoon.configure do |config|
-
-  # 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 tests.
-  #config.mount_at = "/teaspoon"
-
-  # Specifies the root where Teaspoon will look for files. 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`).
-  # Note: Defaults to `Rails.root` if nil.
-  #config.root = nil
-
-  # Paths that will be appended to the Rails assets paths
-  # Note: Relative to `config.root`.
-  #config.asset_paths = ["spec/javascripts", "spec/javascripts/stylesheets"]
-
-  # Fixtures are rendered through a controller, which allows using HAML, RABL/JBuilder, etc. Files in these paths will
-  # be rendered as fixtures.
-  #config.fixture_paths = ["spec/javascripts/fixtures"]
-
-  # SUITES
-  #
-  # You can modify the default suite configuration and create new suites here. Suites are 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 ones defined in the default suite will be used.
-  #
-  # To run a specific suite
-  # - in the browser: http://localhost/teaspoon/[suite_name]
-  # - with the rake task: rake teaspoon suite=[suite_name]
-  # - with the cli: teaspoon --suite=[suite_name]
-  config.suite do |suite|
-
-    # Specify the framework you would like to use. This allows you to select versions, and will do some basic setup for
-    # you -- which you can override with the directives below. This should be specified first, as it can override other
-    # directives.
-    # Note: If no version is specified, the latest is assumed.
-    #
-    # Available: jasmine[1.3.1], mocha[1.10.0, 1.17.1] qunit[1.12.0, 1.14.0]
-    suite.use_framework :mocha
-
-    # Specify a file matcher as a regular expression and all matching files will be loaded when the suite is run. These
-    # files need to be within an asset path. You can add asset paths using the `config.asset_paths`.
-    #suite.matcher = "{spec/javascripts,app/assets}/**/*_spec.{js,js.coffee,coffee}"
-
-    # This suites spec helper, which can require additional support files. This file is loaded before any of your test
-    # files are loaded.
-    #suite.helper = "spec_helper"
-
-    # The core Teaspoon javascripts. It's recommended to include only the base files here, as you can require support
-    # libraries from your spec helper.
-    # Note: For CoffeeScript files use `"teaspoon/jasmine"` etc.
-    #
-    # Available: teaspoon-jasmine, teaspoon-mocha, teaspoon-qunit
-    #suite.javascripts = ["mocha/1.17.1", "teaspoon-mocha"]
-
-    # You can include your own stylesheets if you want to change how Teaspoon looks.
-    # Note: Spec related CSS can and should be loaded using fixtures.
-    #suite.stylesheets = ["teaspoon"]
-
-    # Partial to be rendered in the head tag of the runner. You can use the provided ones or define your own by creating
-    # a `_boot.html.erb` in your fixtures path, and adjust the config to `"/boot"` for instance.
-    #
-    # Available: boot, boot_require_js
-    #suite.boot_partial = "boot"
-
-    # Partial to be rendered in the body tag of the runner. You can define your own to create a custom body structure.
-    #suite.body_partial = "body"
-
-    # Assets to be ignored when generating coverage reports. Accepts an array of filenames or regular expressions. The
-    # default excludes assets from vendor, gems and support libraries.<br/><br/>
-    #suite.no_coverage = [%r{/lib/ruby/gems/}, %r{/vendor/assets/}, %r{/support/}, %r{/(.+)_helper.}]
-
-    # Hooks allow you to use `Teaspoon.hook("fixtures")` before, after, or during your spec run. This will make a
-    # synchronous Ajax request to the server that will call all of the blocks you've defined for that hook name.
-    #suite.hook :fixtures, proc{ }
-
-    # Determine whether specs loaded into the test harness should be embedded as individual script tags or concatenated
-    # into a single file. Similar to Rails' asset `debug: true` and `config.assets.debug = true` options. By default, 
-    # Teaspoon expands all assets to provide more valuable stack traces that reference individual source files.
-    #suite.expand_assets = false
-
-  end
-
-  # Example suite. Since we're just filtering to files already within the root test/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 = "test/javascripts/targeted/*_test.{js,js.coffee,coffee}"
-  #end
-
-  # CONSOLE RUNNER SPECIFIC
-  #
-  # These configuration directives are applicable only when running via the rake task or command line interface. These
-  # directives can be overridden using the command line interface arguments or with ENV variables when using the rake
-  # task.
-  #
-  # Command Line Interface:
-  # teaspoon --driver=phantomjs --server-port=31337 --fail-fast=true --format=junit --suite=my_suite /spec/file_spec.js
-  #
-  # Rake:
-  # teaspoon DRIVER=phantomjs SERVER_PORT=31337 FAIL_FAST=true FORMATTERS=junit suite=my_suite
-
-  # Specify which headless driver to use. Supports PhantomJS and Selenium Webdriver.
-  #
-  # Available: phantomjs, selenium
-  # PhantomJS: https://github.com/modeset/teaspoon/wiki/Using-PhantomJS
-  # Selenium Webdriver: https://github.com/modeset/teaspoon/wiki/Using-Selenium-WebDriver
-  #config.driver = "phantomjs"
-
-  # Specify additional options for the driver.
-  #
-  # PhantomJS: https://github.com/modeset/teaspoon/wiki/Using-PhantomJS
-  # Selenium Webdriver: https://github.com/modeset/teaspoon/wiki/Using-Selenium-WebDriver
-  #config.driver_options = nil
-
-  # Specify the timeout for the driver. Specs are expected to complete within this time frame or the run will be
-  # considered a failure. This is to avoid issues that can arise where tests stall.
-  #config.driver_timeout = 180
-
-  # Specify a server to use with Rack (e.g. thin, mongrel). If nil is provided Rack::Server is used.
-  #config.server = nil
-
-  # Specify a port to run on a specific port, otherwise Teaspoon will use a random available port.
-  #config.server_port = nil
-
-  # Timeout for starting the server in seconds. If your server is slow to start you may have to bump this, or you may
-  # want to lower this if you know it shouldn't take long to start.
-  #config.server_timeout = 20
-
-  # Force Teaspoon to fail immediately after a failing suite. Can be useful to make Teaspoon fail early if you have
-  # several suites, but in environments like CI this may not be desirable.
-  #config.fail_fast = true
-
-  # Specify the formatters to use when outputting the results.
-  # Note: Output files can be specified by using `"junit>/path/to/output.xml"`.
-  #
-  # Available: <%= Teaspoon::Formatters.known_formatters.map(&:name).join ", " %>
-  #config.formatters = ["<%= Teaspoon::Formatters.known_formatters.select(&:default?).first.name %>"]
-
-  # Specify if you want color output from the formatters.
-  #config.color = true
-
-  # Teaspoon pipes all console[log/debug/error] to $stdout. This is useful to catch places where you've forgotten to
-  # remove them, but in verbose applications this may not be desirable.
-  #config.suppress_log = false
-
-  # COVERAGE REPORTS / THRESHOLD ASSERTIONS
-  #
-  # Coverage reports requires Istanbul (https://github.com/gotwarlost/istanbul) to add instrumentation to your code and
-  # display coverage statistics.
-  #
-  # Coverage configurations are similar to suites. You can define several, and use different ones under different
-  # conditions.
-  #
-  # To run with a specific coverage configuration
-  # - with the rake task: rake teaspoon USE_COVERAGE=[coverage_name]
-  # - with the cli: teaspoon --coverage=[coverage_name]
-
-  # Specify that you always want a coverage configuration to be used.
-  #config.use_coverage = nil
-
-  config.coverage do |coverage|
-
-    # Which coverage reports Istanbul should generate. Correlates directly to what Istanbul supports.
-    #
-    # Available: text-summary, text, html, lcov, lcovonly, cobertura, teamcity
-    #coverage.reports = ["text-summary", "html"]
-
-    # The path that the coverage should be written to - when there's an artifact to write to disk.
-    # Note: Relative to `config.root`.
-    #coverage.output_path = "coverage"
-
-    # Various thresholds requirements can be defined, and those thresholds will be checked at the end of a run. If any
-    # aren't met the run will fail with a message. Thresholds can be defined as a percentage (0-100), or nil.
-    #coverage.statements = nil
-    #coverage.functions = nil
-    #coverage.branches = nil
-    #coverage.lines = nil
-
-  end
-
-end

data/lib/generators/teaspoon/install/templates/mocha/spec_helper.coffee

@@ -1,40 +0,0 @@
-# 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 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.
-#
-# For more information: http://github.com/modeset/teaspoon
-#
-# Chai
-# 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()

data/lib/generators/teaspoon/install/templates/mocha/spec_helper.js

@@ -1,40 +0,0 @@
-// 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 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.
-//
-// For more information: http://github.com/modeset/teaspoon
-//
-// Chai
-// 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();