capybara-lockstep 0.3.0 → 0.3.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6e993a9ec82edc1bbea78694f16ae5b3e171255db9eb7e14064922b153d1838d
-  data.tar.gz: 1086e7149ca202b105fd0472c839451845079e05c777a0dba839483fe05c473b
+  metadata.gz: c4c87e5cabd504735dfc07b20021d109d65b74aed53ec173f390c07a2dc6086a
+  data.tar.gz: 2c8f7f1520282284f3b6eb93ddfa0d6109628ee36721c3ba90eba9f05fe565eb
 SHA512:
-  metadata.gz: e54e30ae12effa97dcdbd73d0f07b465b90270efc3ddd3ad83fcde7a4d305164ac0380f7ab3128a37870e78862483659eb01ff6bcdf8fade32cd52c3024d5c31
-  data.tar.gz: c067bf3f9e0be7d6a84668ee7412ea7d93d450f109e8018940e72392277bcc0f5d0ef92717a1692dee8e0443509bc9317a7b403620b6eb62bdb78539ac036098
+  metadata.gz: 0742d9204b35230452220c6cebd3020999f1531530c201180c31ccff3add24973764a232333de5585e3d1180b220535542e1e2c8a04b55b51c5bd388d6578f17
+  data.tar.gz: 93915d9472fe5af20a864de61dc765a0eea708a80cf69bed9d0ccde54c0310e0d0c7767b9bc4a39af1fd4d8270e2a8cd3eea0982e6a0a8a512d09a829ac1f291

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    capybara-lockstep (0.3.0)
+    capybara-lockstep (0.3.1)
       activesupport (>= 3.2)
       capybara (>= 2.0)
       selenium-webdriver (>= 3)

data/README.md

@@ -170,9 +170,13 @@ app.directive('body', function() {
 
 capybara-lockstep will automatically patch Capybara to wait for the browser after every command.
 
-Run your test suite to see if integration was successful and whether stability improves.
+Run your test suite to see if integration was successful and whether stability improves. During validation we recommend to activate `Capybara::Lockstep.debug = true` in your `spec_helper.rb` (RSpec) or `env.rb` (Cucumber). You should see messages like this in your console:
 
-When you run into issues or don't see an effect, try activating `Capybara::Lockstep.debug = true` in your `spec_helper.rb` (RSpec) or `env.rb` (Cucumber).
+```text
+[Capybara::Lockstep] Synchronizing
+[Capybara::Lockstep] Finished waiting for JavaScript
+[Capybara::Lockstep] Synchronized successfully
+```
 
 Note that you may see some failures from tests with wrong assertions, which sometimes passed due to lucky timing.
 
@@ -197,7 +201,9 @@ Capybara::Lockstep.debug = true
 You should now see messages like this during your test runs:
 
 ```
-[Capybara::Lockstep] JavaScript or AJAX requests are running
+[Capybara::Lockstep] Synchronizing
+[Capybara::Lockstep] Finished waiting for JavaScript
+[Capybara::Lockstep] Synchronized successfully
 ```
 
 You may also configure logging to an existing logger object:

data/lib/capybara-lockstep/lockstep.rb

@@ -59,7 +59,7 @@ module Capybara
               self.synchronized = false
             else
               log message_from_js
-              log "Synchronized sucessfully"
+              log "Synchronized successfully"
               self.synchronized = true
             end
           end

data/lib/capybara-lockstep/version.rb

@@ -1,5 +1,5 @@
 module Capybara
   module Lockstep
-    VERSION = "0.3.0"
+    VERSION = "0.3.1"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: capybara-lockstep
 version: !ruby/object:Gem::Version
-  version: 0.3.0
+  version: 0.3.1
 platform: ruby
 authors:
 - Henning Koch