rspec-time-guard 0.1.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2236097d6377167a8f7a07f9d37e1d23ca71110aabdfcf0e6b79ca2d9783c8e5
-  data.tar.gz: d9b596f350b3efef6f8fe67513aa7dd03c933208196cbb31808b8d79e305411b
+  metadata.gz: d69f2e3a7c72240510df20aa4d415f38ef214b875e3e5158767b60f578e024f5
+  data.tar.gz: 79ed632e66858a540b9a73b3616477f43877f6a395e022a64de7959362a283d2
 SHA512:
-  metadata.gz: 3f8aab7a4360a8226ca00e4501eedca92b7c2fdebffcffb89ae5f92e6e7a700b4e225d37445140e6888e8fa58643dea80be4c06d6ef849a02ddb0aa3297532e2
-  data.tar.gz: 006735ff24aa6e288d72d043f7efad35169d4af3c481de695ae3dcc2d5cfc868cc29c28139c7107badf77025fbee846a2e90885e6556d709822982711bf23e81
+  metadata.gz: c9dad05a04963ee2ca7bbb561cd219a99e03869fb42d5e77af3045e3ce4affccd8c606802682c48c2f30b925417ae80dc0cb65c0c8dc27246c8973887dcde3e1
+  data.tar.gz: 98c02103e8ae43889661e373c0544c60fd9fffee2e78f79049653bffdd3bf05b6721f38d053a7b51d2543822e6e58a75fe0a575159f4867441ebd022db867003

data/CHANGELOG.md

@@ -1,4 +1,12 @@
-## [Unreleased]
+## [0.2.1] - 2026-10-28
+- Use monotonic clock to prevent false timeouts with Timecop
+- Drop invalid `Exception` rescue clause
+- Remove useless logging from Railtie
+- Bump json dependency
+
+## [0.2.0] - 2025-04-22
+- Experimental new implementation, using a single-threaded monitoring approach
+
 
 ## [0.1.0] - 2025-03-11
 

data/README.md

@@ -1,33 +1,32 @@
-[//]: # (TODO: Add a public TODO list?)
-
-# ⚠️ **_This project is a Work In Progress_** ⚠️
-
 # RspecTimeGuard
 
-`RspecTimeGuard` helps you identify and manage slow-running tests in your RSpec test suite by setting time limits on individual examples or globally across your test suite.
+`RspecTimeGuard` monitors your tests as they run and provides safeguards against tests that take too long, helping you maintain a fast, reliable test suite.
 
+Why `RspecTimeGuard`?
+- **🔍 Catches slow tests** with customizable time limits and warnings
+- **🛑 Prevents runaway tests** from blocking your CI pipeline
+- **📊 Identifies bottlenecks** in your test suite to help you optimize
 
-## Installation
 
-Add this line to your application's Gemfile:
+## Quick Start
 
 ```ruby
+# Add to your Gemfile
 gem 'rspec-time-guard'
-```
-
-And then execute:
 
-```bash
-$ bundle install
+# In spec_helper.rb or rails_helper.rb
+require 'rspec_time_guard'
 ```
 
-Or install it globally:
+Tag individual tests with specific time limits:
 
-```bash
-$ gem install rspec-time-guard
+```ruby
+it "completes quickly", time_limit_seconds: 0.5 do
+  # This test will fail if it takes more than 0.5 seconds
+  expect(fast_operation).to be_truthy
+end
 ```
 
-
 ## Usage
 
 ### Basic Setup
@@ -56,7 +55,7 @@ Create an initializer at `config/initializers/rspec_time_guard.rb` (for Rails) o
 RspecTimeGuard.configure do |config|
   # Set a global time limit in seconds for all examples (nil = no global limit)
   config.global_time_limit_seconds = 1.0
-  
+
   # Whether to continue running tests that exceed their time limit
   # true = shows warning but allows test to complete
   # false = raises TimeLimitExceededError and stops the test (default)
@@ -91,7 +90,7 @@ describe "operations that need more time", time_limit_seconds: 5 do
   it "does a complex operation" do
     # ...
   end
-  
+
   it "does another complex operation" do
     # ...
   end
@@ -149,7 +148,7 @@ RSpec.describe User, type: :model do
     user = User.new(email: "invalid")
     expect(user.valid?).to be false
   end
-  
+
   # This test will use the global time limit if configured
   it "can generate a profile" do
     user = User.create(name: "John", email: "john@example.com")
@@ -168,6 +167,11 @@ RSpec Time Guard works by:
 3. Monitoring execution time
 4. Taking action if the time limit is exceeded
 
+## Performance and Feedback
+
+RSpec Time Guard is a relatively new gem, and while our initial benchmarks show promising results, we're still gathering comprehensive performance data across different environments and use cases. The gem's impact on your test suite may vary depending on factors like test suite size, Ruby interpreter, and CI environment.
+
+I'd love to hear about your experience using RSpec Time Guard.
 
 ## Contributing
 

data/lib/rspec_time_guard/railtie.rb

@@ -3,11 +3,7 @@
 module RspecTimeGuard
   class Railtie < Rails::Railtie
     initializer "rspec_time_guard.configure" do
-      Rails.logger.info("INITIALIZER")
-
       config.after_initialize do
-        Rails.logger.info("AFTER INITIALIZE")
-
         if defined?(RSpec) && Rails.env.test?
           require "rspec_time_guard"
 

data/lib/rspec_time_guard/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module RspecTimeGuard
-  VERSION = "0.1.0"
+  VERSION = "0.2.1"
 end

data/lib/rspec_time_guard.rb

@@ -7,6 +7,94 @@ require "rspec_time_guard/railtie" if defined?(Rails)
 module RspecTimeGuard
   class TimeLimitExceededError < StandardError; end
 
+  class TimeoutMonitor
+    def initialize
+      @active_tests = {}
+      @mutex = Mutex.new
+      @monitor_thread = nil
+    end
+
+    def register_test(example, timeout, thread)
+      @mutex.synchronize do
+        @active_tests[example.object_id] = {
+          example: example,
+          start_time: Process.clock_gettime(Process::CLOCK_MONOTONIC),
+          timeout: timeout,
+          thread_id: thread.object_id,
+          warned: false
+        }
+
+        # NOTE: We start monitor thread if not already running
+        start_monitor_thread if @monitor_thread.nil? || !@monitor_thread.alive?
+      end
+    end
+
+    def unregister_test(example)
+      @mutex.synchronize do
+        @active_tests.delete(example.object_id)
+      end
+    end
+
+    private
+
+    def start_monitor_thread
+      @monitor_thread = Thread.new do
+        Thread.current[:name] = "rspec_time_guard_monitor"
+
+        loop do
+          check_for_timeouts
+          sleep 0.5 # Check every half second, adjust as needed
+
+          # Exit thread if no more tests to monitor
+          break if @mutex.synchronize { @active_tests.empty? }
+        end
+      end
+    end
+
+    def check_for_timeouts
+      now = Process.clock_gettime(Process::CLOCK_MONOTONIC)
+      timed_out_examples = []
+
+      @mutex.synchronize do
+        @active_tests.each do |_, info|
+          elapsed = now - info[:start_time]
+          timed_out_examples << info[:example] if elapsed > info[:timeout]
+        end
+      end
+
+      # NOTE: We handle timeouts outside the mutex to avoid deadlocks
+      timed_out_examples.each do |example|
+        group_name = example.example_group.description
+        test_name = example.description
+        timeout = @active_tests[example.object_id][:timeout]
+        elapsed = now - @active_tests[example.object_id][:start_time]
+        thread = begin
+          ObjectSpace._id2ref(@active_tests[example.object_id][:thread_id])
+        rescue
+          nil
+        end
+
+        next unless thread.alive?
+
+        # NOTE: We create an error for RSpec to report
+        error = TimeLimitExceededError.new("Test '#{group_name} #{test_name}' timed out after #{timeout}s (took #{elapsed.round(2)}s)")
+        error.set_backtrace(thread.backtrace || [])
+
+        if RspecTimeGuard.configuration.continue_on_timeout
+          next if @active_tests[example.object_id][:warned]
+
+          warn "WARNING [RSpecTimeGuard] - #{error.message}"
+
+          @active_tests[example.object_id][:warned] = true
+        else
+          # NOTE: We use Thread.raise which is safer than Thread.kill
+          # This allows the thread to clean up properly
+          thread.raise(error)
+        end
+      end
+    end
+  end
+
   class << self
     def configure
       yield(configuration)
@@ -16,10 +104,16 @@ module RspecTimeGuard
       @_configuration ||= RspecTimeGuard::Configuration.new
     end
 
-    # TODO: Handle RSpec summary manually?
-    # TODO: Check that it doesn't break RSpec parallel runs in CI (if any)
+    def monitor
+      @_monitor ||= TimeoutMonitor.new
+    end
+
+    # TODO: Write article (in 2 parts?)
+    # TODO: check warnings on test suite
+    # TODO: CHeck how it works with other Ruby interpreters? (check which implem was tested)
+    # TODO: Handle RSpec summary manually
+    #   -> Add a TimeGuard section
     # TODO: Run profiling on the whole test suite to check for performance issues
-    # TODO: add PR template
     def setup
       RSpec.configure do |config|
         config.around(:each) do |example|
@@ -27,36 +121,12 @@ module RspecTimeGuard
 
           next example.run unless time_limit_seconds
 
-          completed = false
-
-          # NOTE: We instantiate a monitoring thread, to allow the example to run in the main RSpec thread.
-          # This is required to keep the RSpec context.
-          monitor_thread = Thread.new do
-            Thread.current.report_on_exception = false
-
-            # NOTE: The following logic:
-            #  - Waits for the duration of the time limit
-            #  - If the main thread is still running at that stage, raises a TimeLimitExceededError
-            sleep time_limit_seconds
-
-            unless completed
-              message = "[RspecTimeGuard] Example exceeded timeout of #{time_limit_seconds} seconds"
-              if RspecTimeGuard.configuration.continue_on_timeout
-                warn "#{message} - Running the example anyway (:continue_on_timeout option set to TRUE)"
-                example.run
-              else
-                Thread.main.raise RspecTimeGuard::TimeLimitExceededError, message
-              end
-            end
-          end
+          RspecTimeGuard.monitor.register_test(example, time_limit_seconds, Thread.current)
 
-          # NOTE: Main RSpec thread execution
           begin
             example.run
-            completed = true
           ensure
-            # NOTE: We explicitly clean up the monitoring thread in case the example completes before the time limit.
-            monitor_thread.kill if monitor_thread.alive?
+            RspecTimeGuard.monitor.unregister_test(example)
           end
         end
       end

metadata

@@ -1,14 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: rspec-time-guard
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Lucas Montorio
-autorequire:
 bindir: exe
 cert_chain: []
-date: 2025-04-03 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -66,7 +65,6 @@ metadata:
   homepage_uri: https://github.com/LucasMontorio/rspec-time-guard
   source_code_uri: https://github.com/LucasMontorio/rspec-time-guard
   changelog_uri: https://github.com/LucasMontorio/rspec-time-guard/blob/main/CHANGELOG.md
-post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -81,8 +79,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.11
-signing_key:
+rubygems_version: 4.0.16
 specification_version: 4
 summary: A simple time keeper for RSpec tests.
 test_files: []