capybara-lockstep 2.2.0 → 2.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fa4a510d3f4745ef60812fdf3ab03f6c3e8ede0c6ea4046cb87364d6664e2a7d
-  data.tar.gz: 78be38bdb5aa4fcb9147394ac3adb11f3112c18539ba53a096c214931be753cb
+  metadata.gz: 8bad1a61632d37c5e705b886be4cb840a62923f73887c1443060fb00c6e69aa2
+  data.tar.gz: 9243b559659a33a00e6f803304284aa9cd47e5c2f110a11b47eb2e4e62441537
 SHA512:
-  metadata.gz: 356df47acf01a2642769be49f54c48736ea030c803a92b3c059c587e5e82bb927fa0b4e5dcf7953060162a46491cf0122c6a2d0debd1f607cbd1b09cc8608ff2
-  data.tar.gz: c5d1189ee309d32197f19765dad9014cc59f13a8d9f6a17287537045cbf02664b480ce9d087e933b3fad1a2c63b4460b5dc5e61e20d3e0b98d76cde9d90eaff3
+  metadata.gz: 9b285d685609f913c92b4b8d5556d34d7d77e2fb6d80e5fac4cda189c81a2b81445fc65a5680726c2d21b16d0bcdcb1fcb35e3a6169b2febca3244eaa555b985
+  data.tar.gz: d598437ffb3eaf066d6cbcb747ac6c5445bed0a2c2cbc5113f42e0d947d4b71fc7bb4752ede4193cca989acafd5d126757c67d3454fbfc226014d7b42056b55f

data/CHANGELOG.md

@@ -2,6 +2,10 @@ All notable changes to this project will be documented in this file.
 
 This project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
 
+# 2.2.1
+
+- Fixed a bug that disabled most functionality for drivers with `browser: :remote`.
+
 
 # 2.2.0
 

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    capybara-lockstep (2.2.0)
+    capybara-lockstep (2.2.1)
       activesupport (>= 4.2)
       capybara (>= 3.0)
       ruby2_keywords
@@ -31,7 +31,7 @@ GEM
     childprocess (4.1.0)
     concurrent-ruby (1.1.10)
     daemons (1.4.1)
-    diff-lcs (1.3)
+    diff-lcs (1.5.1)
     eventmachine (1.2.7)
     gemika (0.8.1)
     i18n (1.12.0)
@@ -58,21 +58,21 @@ GEM
     rake (13.1.0)
     regexp_parser (2.8.2)
     rexml (3.2.5)
-    rspec (3.7.0)
-      rspec-core (~> 3.7.0)
-      rspec-expectations (~> 3.7.0)
-      rspec-mocks (~> 3.7.0)
-    rspec-core (3.7.0)
-      rspec-support (~> 3.7.0)
-    rspec-expectations (3.7.0)
+    rspec (3.13.0)
+      rspec-core (~> 3.13.0)
+      rspec-expectations (~> 3.13.0)
+      rspec-mocks (~> 3.13.0)
+    rspec-core (3.13.0)
+      rspec-support (~> 3.13.0)
+    rspec-expectations (3.13.1)
       diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.7.0)
-    rspec-mocks (3.7.0)
+      rspec-support (~> 3.13.0)
+    rspec-mocks (3.13.1)
       diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.7.0)
-    rspec-support (3.7.0)
-    rspec-wait (0.0.9)
-      rspec (>= 3, < 4)
+      rspec-support (~> 3.13.0)
+    rspec-support (3.13.1)
+    rspec-wait (0.0.10)
+      rspec (>= 3.0)
     ruby2_keywords (0.0.5)
     rubyzip (2.3.2)
     selenium-webdriver (4.1.0)

data/README.md

@@ -2,14 +2,14 @@
 
 This Ruby gem synchronizes [Capybara](https://github.com/teamcapybara/capybara) commands with client-side JavaScript and AJAX requests. This greatly improves the stability of an end-to-end ("E2E") test suite, even if that suite has timing issues.
 
-The next section explain why your test suite is flaky and how capybara-lockstep can help.\
+The next section explains why your test suite is flaky and how capybara-lockstep can help.\
 If you don't care you may **skip to [installation instructions](#installation)**.
 
 
 Why are tests flaky?
 --------------------
 
-A naively written E2E test will have [race conditions](https://makandracards.com/makandra/47336-fixing-flaky-integration-tests) between the test script and the controlled browser. How often these timing issues will fail your test depends on luck and your machine's performance. You may not see these issues for years until a colleague runs your suite on their new laptop.
+A naively written E2E test will have [race conditions](https://makandracards.com/makandra/47336-fixing-flaky-integration-tests) between the test script and the controlled browser. How often these timing issues will cause your tests to fail depends on luck and your machine's performance. You may not see these issues for years until a colleague runs your suite on their new laptop.
 
 Here is a typical example for a test that will fail with unlucky timing:
 
@@ -26,10 +26,10 @@ end
 
 This test has four timing issues that may cause it to fail:
 
-1. We click on the *New tweet* button, but the the JS event handler to open the tweet form wasn't registered yet.
-2. We start filling in the form, but it wasn't loaded yet.
+1. We click on the *New tweet* button, but the JS event handler to open the tweet form hasn't been registered yet.
+2. We start filling in the form, but it hasn't been loaded yet.
 3. After sending the tweet we immediately navigate away, killing the form submission request that is still in flight. Hence the tweet will never appear in the next step.
-4. We look for the new tweet, but the timeline wasn't loaded yet.
+4. We look for the new tweet, but the timeline hasn't been loaded yet.
 
 [Capybara will retry](https://github.com/teamcapybara/capybara#asynchronous-javascript-ajax-and-friends) individual commands or expectations when they fail.\
 However, only issues **2** and **4** can be healed by retrying.
@@ -71,10 +71,10 @@ When capybara-lockstep synchronizes it will:
 - wait for client-side JavaScript to render or hydrate DOM elements.
 - wait for any pending AJAX requests to finish and their callbacks to be called.
 - wait for dynamically inserted `<script>`s to load (e.g. from [dynamic imports](https://webpack.js.org/guides/code-splitting/#dynamic-imports) or Analytics snippets).
-- waits for dynamically inserted `<img>` or `<iframe>` elements to load (ignoring [lazy-loaded](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#lazy) elements).
-- waits for dynamically inserted `<audio>` and `<video>` elements to load their [metadata](https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/loadedmetadata_event)
+- wait for dynamically inserted `<img>` or `<iframe>` elements to load (ignoring [lazy-loaded](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#lazy) elements).
+- wait for dynamically inserted `<audio>` and `<video>` elements to load their [metadata](https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/loadedmetadata_event)
 
-In summary Capybara can no longer observe or interact with the page while HTTP requests are in flight.
+In summary, Capybara can no longer observe or interact with the page while HTTP requests are in flight.
 This covers most async work that causes flaky tests.
 
 
@@ -84,7 +84,6 @@ Async work not synchronized by capybara-lockstep includes:
 
 - Animations
 - Websocket connections
-- Media elements (`<video>`, `<audio>`)
 - Service workers
 - Work scheduled via `setTimeout()` or `setInterval()`.
 
@@ -100,13 +99,14 @@ Check if your application satisfies all requirements for capybara-lockstep:
 
 - Capybara 2.0 or higher.
 - Your Capybara driver must use [selenium-webdriver](https://rubygems.org/gems/selenium-webdriver/) 3.0 or higher. capybara-lockstep deactivates itself for any other driver.
+  There is a [fork](https://github.com/Skalar/capybara-lockstep/tree/playwright-driver) with support for [capybara-playwright-driver](https://github.com/YusukeIwaki/capybara-playwright-driver).
 - This gem was only tested with a Selenium-controlled Chrome browser. [Chrome in headless mode](https://makandracards.com/makandra/492109-running-capybara-tests-in-headless-chrome) is recommended, but not required.
 - This gem was only tested with Rails, but there's no Rails dependency.
 
 
 ### Installing the Ruby gem
 
-Assuming that you're using Rails Add this line to your application's `Gemfile`:
+Assuming that you're using Rails, add this to your application's `Gemfile`:
 
 ```ruby
 group :test do
@@ -142,9 +142,9 @@ Ideally the snippet should be included in the `<head>` before any other `<script
 
 ### Including the middleware (optional)
 
-This gem provides a Rack middleware to block Capybara while your Rails (or Rack) backend is busy.
+This gem provides Rack middleware to block Capybara while your Rails (or Rack) backend is busy.
 
-Using the middleware is optional, as the [JavaScript snippet](#including-the-javascript-snippet-required) already for AJAX requests on the client. However, using the middleware covers some additional edge cases. For example, the middleware detects requests that were aborted on the frontend, but are still being processed by the backend.
+Using the middleware is optional, as the [JavaScript snippet](#including-the-javascript-snippet-required) already waits for asynchronous work on the client. However, using the middleware covers some additional edge cases. For example, the middleware detects requests that were aborted on the frontend, but are still being processed by the backend.
 
 To include the middleware in a Rails application, add the following line to `config/environments/test.rb`:
 

data/lib/capybara-lockstep/capybara_ext.rb

@@ -3,36 +3,46 @@ require 'ruby2_keywords'
 module Capybara
   module Lockstep
     module SynchronizeMacros
+      def self.extended(by)
+        by.instance_eval do
+          prepend(@synchronize_before_module = Module.new)
+          prepend(@synchronize_after_module = Module.new)
+          prepend(@unsynchronize_after_module = Module.new)
+        end
+      end
 
       def synchronize_before(meth, lazy:)
-        mod = Module.new do
+        @synchronize_before_module.module_eval do
           define_method meth do |*args, &block|
-            Lockstep.auto_synchronize(lazy: lazy, log: "Synchronizing before ##{meth}")
+            @synchronize_before_count ||= 0
+            @synchronize_before_count += 1
+            Lockstep.auto_synchronize(lazy: lazy, log: "Synchronizing before ##{meth}") if @synchronize_before_count == 1
             super(*args, &block)
+          ensure
+            @synchronize_before_count -= 1
           end
 
           ruby2_keywords meth
         end
-
-        prepend(mod)
       end
 
       def synchronize_after(meth)
-        mod = Module.new do
+        @synchronize_after_module.module_eval do
           define_method meth do |*args, &block|
+            @synchronize_after_count ||= 0
+            @synchronize_after_count += 1
             super(*args, &block)
           ensure
-            Lockstep.auto_synchronize
+            Lockstep.auto_synchronize(log: "Synchronizing after ##{meth}") if @synchronize_after_count == 1
+            @synchronize_after_count -= 1
           end
 
           ruby2_keywords meth
         end
-
-        prepend(mod)
       end
 
       def unsynchronize_after(meth)
-        mod = Module.new do
+        @unsynchronize_after_module.module_eval do
           define_method meth do |*args, &block|
             super(*args, &block)
           ensure
@@ -41,10 +51,7 @@ module Capybara
 
           ruby2_keywords meth
         end
-
-        prepend(mod)
       end
-
     end
   end
 end
@@ -158,23 +165,23 @@ Capybara::Session.class_eval do
   synchronize_around_script_method :evaluate_async_script
 end
 
-# Capybara 3 has driver-specific Node classes which sometimes
-# super to Capybara::Selenium::Node, but not always.
-node_classes = [
+# In Capybara 3 there are the specialized classes for nodes for most browers.
+# We need to patch relevant methods on all of these.
+driver_specific_node_classes = [
   (Capybara::Selenium::ChromeNode  if defined?(Capybara::Selenium::ChromeNode)),
   (Capybara::Selenium::FirefoxNode if defined?(Capybara::Selenium::FirefoxNode)),
   (Capybara::Selenium::SafariNode  if defined?(Capybara::Selenium::SafariNode)),
   (Capybara::Selenium::EdgeNode    if defined?(Capybara::Selenium::EdgeNode)),
   (Capybara::Selenium::IENode      if defined?(Capybara::Selenium::IENode)),
-].compact
+].compact.freeze
 
-if node_classes.empty?
-  # Capybara 2 has no driver-specific Node implementations,
-  # so we patch the shared base class.
-  node_classes = [Capybara::Selenium::Node]
-end
+# For other browsers (like the :remote browser) we instead get a generic node class.
+# This is also the case for Capybara 2.
+generic_node_classes = [
+  Capybara::Selenium::Node,
+].freeze
 
-node_classes.each do |node_class|
+[*driver_specific_node_classes, *generic_node_classes].each do |node_class|
   node_class.class_eval do
     extend Capybara::Lockstep::SynchronizeMacros
 

data/lib/capybara-lockstep/version.rb

@@ -1,5 +1,5 @@
 module Capybara
   module Lockstep
-    VERSION = "2.2.0"
+    VERSION = "2.2.1"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: capybara-lockstep
 version: !ruby/object:Gem::Version
-  version: 2.2.0
+  version: 2.2.1
 platform: ruby
 authors:
 - Henning Koch
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2024-02-12 00:00:00.000000000 Z
+date: 2024-06-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: capybara
@@ -124,7 +124,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.4.3
+rubygems_version: 3.4.1
 signing_key: 
 specification_version: 4
 summary: Synchronize Capybara commands with client-side JavaScript and AJAX requests