TestSquad
Running JavaScript tests on your Rails app, the easy way.
- Supports QUnit, Ember.js, Mocha and Jasmine
- Go headless with Phantom.js
- Colored output
- Asset pipeline support
Installation
Add these lines to your application's Gemfile:
group :development, :test do
gem 'test_squad'
end
And then execute:
$ bundle
Usage
After installing TestSquad, generate your tests skeleton. The generator will detect if you're using RSpec or TestUnit and will generate the javascript
directory basead on that detection. Just use the command rails generate test_squad:install --framework FRAMEWORK
.
$ rails generate test_squad:install --framework jasmine
create test/javascript/squad_sample
create test/javascript/squad_sample/.keep
create test/javascript/spec_helper.js
source https://rails-assets.org
exist test/javascript
create test/javascript/test_squad.rb
Running tests
You can run your tests with rake test_squad
. You can also visit http://localhost:3000/tests
for in-browser testing.
Configure Ember
When using the Ember framework, you must configure your application name. It'll default to your Rails application name.
//= require application
//= require_self
//= require_tree ./components
//= require_tree ./models
//= require_tree ./routes
//= require_tree ./unit
//= require_tree ./views
// Set the application.
App = SquadSample;
// Set up Ember testing.
App.rootElement = '#ember-testing';
App.setupForTesting();
App.injectTestHelpers();
To disable all Ember logging, add the following line to test_helper.js
, just before the //= require application
line.
//= require ./logging
Then create the file spec/javascript/logging.js
with this content:
Ember = {ENV: {
LOG_TRANSITIONS: false,
LOG_VIEW_LOOKUPS: false,
LOG_ACTIVE_GENERATION: false,
LOG_RESOLVER: false,
LOG_TRANSITIONS: false,
LOG_TRANSITIONS_INTERNAL: false,
LOG_VERSION: false
}};
Configure Mocha
By default, Mocha is configured with expect.js. You can use different libraries like should.js or chai.
Just add the dependency to your Gemfile
. Use rails-assets-chai
or rails-assets-should
:
source 'https://rubygems.org'
source 'https://rails-assets.org'
gem 'rails', '4.2.0'
gem 'sass-rails', '~> 5.0'
gem 'uglifier', '>= 1.3.0'
gem 'ember-rails'
gem 'rails-assets-jquery'
group :development, :test do
gem 'test_squad', path: '../../test_squad'
gem 'rails-assets-mocha'
gem 'rails-assets-chai'
end
Install the dependency with bundle install
. Then require the library on {test/spec}/javascript/spec_helper.js
.
//= require application
//= require chai
//= require_self
//= require_tree ./squad_sample
var assert = chai.assert;
mocha.setup('bdd');
mocha.checkLeaks();
mocha.globals(['jQuery']);
mocha.reporter(mocha.TestSquad);
window.onload = function(){
mocha.run();
};
Troubleshooting
If you have a catch-all route, add the following line to your config/routes.rb
file. This will be required if you configure Ember.js to use history.pushState
.
get :tests, to: 'test_squad#tests' unless Rails.env.production?
Otherwise you won't be able to to run your in-browser tests.
Configuration
The rake task accepts some env variables.
HOST
: the binding host. Defaults tolocalhost
.PORT
: the server port. Defaults to50000
.TIMEOUT
: how much time a test can take. Defaults to10
(seconds).LOG
: set if console messages should be logged. Defaults tofalse
.PHANTOMJS_BIN
: set the PhantomJS binary. Defaults tophantomjs
.
Contributing
Before starting, create an issue asking if it'd be a useful/wanted feature. This will avoid wasting your time.
- Fork it ( http://github.com/fnando/test_squad/fork )
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create new Pull Request
Remember:
- Don't mess with versioning.
- Follow the code style already present.
- Opening an issue asking if your feature/change will be welcomed it's recommended. That way you don't waste your time.
License
(The MIT License)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.