protractor-rails 0.0.6 → 0.0.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 950a16a0f023f3702d23caa7db7f8896b1789ee4
-  data.tar.gz: 0a26d0ec37a3eacf5b58d8345975257ae8a3e055
+  metadata.gz: 6fd62769107f64872318aeb898dc560f3f03ada6
+  data.tar.gz: 60a4e36af9c4e21c41d4af92baa9d25571e086d0
 SHA512:
-  metadata.gz: 2a9210d7aa93cfd8984ecd7837bc299bff3e8df43789a14a091868b3675e6a67163855c769e10f366a3054f8377297aaadf9c647ac9e4b2d1cd37fe3d846d008
-  data.tar.gz: a07d45913dc7b0c40091b8fe7c5111cd5d944cf4315a717850e2aec48b73d8b1ef2610f2f9dc59cbfc28dc44080049d600a2367164d62b515885066f0fba0f7d
+  metadata.gz: 0c29977fed8f5157f1c210ab5c97a3c607a9391cae9532ee448f18c8267a2cb660c159cc62191fe4b0e607a1d97b179e968ef9a7d395ba50e08dcf898679574e
+  data.tar.gz: 65afd32e77cb103e4f3b790f707ee65fc097ae847036daee0b7de78d75f77b9ff250bca4fadcd6efe6affb34280e2fefb45fcc58c332861aff3fc36ef3df4c5b

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    protractor-rails (0.0.6)
+    protractor-rails (0.0.7)
       colorize
       railties
 

data/README.md

@@ -45,7 +45,7 @@ If everything starts up and runs cleanly you should see the test summary of 1 te
 ### 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.
+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**
 
@@ -78,7 +78,13 @@ If I have a directory set up for protractor specs in `spec/javascripts/protracto
 
 ```
 
-Once you have setup your tests as above, running `rake protractor:spec` will pick up new tests and run them for you`
+Once you have setup your tests as above, running `rake protractor:spec` will pick up new tests and run them for you.
+
+You can specify the binding for the rails server as an environment variable: `rake protractor:spec rails_binding=hostname_or_ip`.
+
+You can run specific test suites by passing in options to the rake task as per the below example.
+
+    $ rake protractor:spec --suite suite-name
 
 ### Setup and teardown
 
@@ -102,7 +108,7 @@ rspec tests. Keep your integration tests to a minimum and test as much as possib
 
 **Contributions, questions, comments, threats or suggestions are welcome.**
 
-1. Fork it ( http://github.com/<my-github-username>/protractor-rails/fork )
+1. Fork it (http://github.com/my-github-username/protractor-rails/fork)
 2. Create your feature branch (`git checkout -b my-new-feature`)
 3. Commit your changes (`git commit -am 'Add some feature'`)
 4. Push to the branch (`git push origin my-new-feature`)

data/lib/protractor/rails/version.rb

@@ -1,5 +1,5 @@
 module Protractor
   module Rails
-    VERSION = "0.0.6"
+    VERSION = "0.0.7"
   end
 end

data/lib/tasks/protractor.rake

@@ -1,4 +1,6 @@
-namespace :protractor do
+require 'optparse'
+
+namespace :protractor do |args|
   desc "starts protractor example test to see if you have your system set up correctly"
   task :example do
     begin
@@ -18,6 +20,15 @@ namespace :protractor do
   desc "Run specs from spec/javascripts/protractor.conf.js"
   task :spec do
     begin
+      options = ''
+      OptionParser.new(args) do |opts|
+        # Suite setup
+        suiteKey = '--suite'
+        opts.on("#{suiteKey} {suite}", 'Test suite name', String) do |suite|
+          options = options + "#{suiteKey} #{suite}"
+        end
+      end.parse!
+
       webdriver_pid = fork do
         Rake::Task['protractor:webdriver'].invoke
       end
@@ -28,7 +39,7 @@ namespace :protractor do
       puts "Rails Server PID: #{rails_server_pid}".yellow.bold
       puts "Waiting for servers to finish starting up...."
       sleep 6
-      success = system 'protractor spec/javascripts/protractor.conf.js'
+      success = system "protractor #{options} spec/javascripts/protractor.conf.js"
       Process.kill 'TERM', webdriver_pid
       Process.kill 'TERM', rails_server_pid
       Process.wait webdriver_pid
@@ -69,7 +80,11 @@ namespace :protractor do
 
   task :rails do
     puts "Starting Rails server on port 4000 pid file in tmp/pids/protractor_test_server.pid".green
-    system 'rails s -e test --port=4000 -P tmp/pids/protractor_test_server.pid'
+    rails_command = "rails s -e test -P tmp/pids/protractor_test_server.pid --port=4000"
+    if ENV['rails_binding'] != nil
+      rails_command << " --binding #{ ENV['rails_binding'] }"
+    end
+    system rails_command
   end
 
   task :webdriver do

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: protractor-rails
 version: !ruby/object:Gem::Version
-  version: 0.0.6
+  version: 0.0.7
 platform: ruby
 authors:
 - Tyrone Wilson
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-09-09 00:00:00.000000000 Z
+date: 2014-10-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler