protractor-rails 0.0.2 → 0.0.3.pre.alpha

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: c2d19507f5e5cad0d7b0637528266cd95a11b7fb
-  data.tar.gz: 556d7f32fd514d753a44cd5cedbe95b57e1678a0
+  metadata.gz: e6f03720412a3f8fc6787ca747cb3fe28b025217
+  data.tar.gz: 1c26cf1698d96e2e4fdd3bce8d8ebd739b63ae04
 SHA512:
-  metadata.gz: 967de443c66e8bf2cfad70734b0afab04a43b5aad6c5c192d10e665271fa1736cfd9e0666c55b0a25bd65b2ec2212033ade3e51e512ccf9fc15c52ca1d45bd35
-  data.tar.gz: 2bc78a1f6fa73387298da3bf04b01f5a55ed9ac16b2b56899c5d2eb909b118816d8180ea77619ed71646b248cda9b97fbf5f4bb0f9c97195d35d54a2655072eb
+  metadata.gz: 71f1d12ed657772737cc6f7a02e148bed79f0a8a4227b95031754d5ca504bc84220fbf49ab72d1c29abe2bdba32c56ae2e4548a444739116226fd6ee8fc9fc34
+  data.tar.gz: 3d432682563e6de3d6db220e6522e2875e8cf4a690d15b9d8e59d53f4758c87e681d743d4e2abd6dc4ab9022ab150727d7ab8ecf41090638821a5919b02bc472

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    protractor-rails (0.0.2)
+    protractor-rails (0.0.3.pre.alpha)
       colorize
       railties
 

data/README.md

@@ -1,8 +1,6 @@
 # Protractor::Rails
 
-This gem helps you to not go through the same pain that I did trying to figure out the best way to run angularjs e2e tests in a rails application.
-
-NB: This gem is in pre-release so don't use it yet.
+This gem helps you seemlessly setup, run and maintain a angularjs e2e test suite using protractor in a rails application.
 
 ## Installation
 
@@ -25,6 +23,76 @@ NB: This uses `sudo` so you will need to enter your password
 
 ## Usage
 
+### Initialization
+
+You can initialize your app with protractor rails by running
+
+    $ rake protractor:init
+
+### Dummy test in local environment
+
+This will generate and template configuration and a dummy example test. Once you have run this you can test that
+everything has been set up correctly in your local environment by running the following command:
+
+    $ rake protractor:spec
+
+This will run a local rails test server, the webdriver selenium server and run protractor against the example_spec.js
+If everything starts up and runs cleanly you should see the test summary of 1 test 1 pass and 0 failures.
+
+### Running your tests
+
+When the `rake protractor:init` script is run it will create a file `spec/javascripts/protractor.conf.js`. This file is where you
+can configure the tests that should be run. [See Protractor Documentation for more details]:https://github.com/angular/protractor/blob/master/docs/getting-started.md.
+
+In this file you can provide patterns for matching your protractor specs. **NB: It is recommended that you use a subdirectory such as spec/javascripts/protractor_specs for easy matching and organization**
+
+**Example**
+
+If I have a directory set up for protractor specs in `spec/javascripts/protractor_specs/`, my configuration file would look something like the below
+
+```
+  // An example configuration file.
+  exports.config = {
+    // The address of a running selenium server.
+    seleniumAddress: 'http://localhost:4444/wd/hub',
+
+    // Capabilities to be passed to the webdriver instance.
+    capabilities: {
+        'browserName': 'chrome'
+    },
+
+    // Spec patterns are relative to the current working directly when protractor is called
+    specs: ['protractor_specs/**/*.js '],
+
+    baseUrl: 'http://localhost:4000',
+
+    // Options to be passed to Jasmine-node.
+    jasmineNodeOpts: {
+        showColors: true,
+        defaultTimeoutInterval: 30000
+    },
+};
+
+```
+
+Once you have setup your tests as above, running `rake protractor:spec will pic up new tests and run them for you`
+
+### Setup and teardown
+
+There is a task to reset your database to remove items you have created during your tests. This will also seed your database with any fixtures you might have prepared
+
+    $ rake protractor:cleanup
+
+This will reset your test database and load in seeds in db/seeds.rb into your test database only.
+
+There is also a convenience function for running cleanup after you have run your tests ready for the next test run.
+
+    $ rake protractor:spec_and_cleanup
+
+## Notes about integration tests
+
+Integration tests are **MUCH** faster than testing things yourself but they are MUCH slower than running unit tests or
+rspec tests. Keep your integration tests to a minimum and test as much as possible with your normal rails test suite.
 
 
 ## Contributing

data/lib/protractor/rails/version.rb

@@ -1,5 +1,5 @@
 module Protractor
   module Rails
-    VERSION = "0.0.2"
+    VERSION = "0.0.3-alpha"
   end
 end

data/lib/tasks/protractor.rake

@@ -77,7 +77,18 @@ namespace :protractor do
   end
 
   task :cleanup do
-    puts "rake db:test:prepare to cleanup for the next test session".green.bold
+    puts "rake db:test:prepare to cleanup for the next test session".green
     system 'rake db:test:prepare --trace'
+    puts "Seeding the test database....".green
+    system "rake db:test:seed --trace"
+  end
+end
+
+namespace :db do
+  namespace :test do
+    desc "seed only the test database (Task provided by protractor-rails)"
+    task :seed do
+      system "rake db:seed RAILS_ENV=test"
+    end
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: protractor-rails
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.3.pre.alpha
 platform: ruby
 authors:
 - Tyrone Wilson
@@ -106,9 +106,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">="
+  - - ">"
     - !ruby/object:Gem::Version
-      version: '0'
+      version: 1.3.1
 requirements: []
 rubyforge_project: 
 rubygems_version: 2.2.2