rspec_n 2.0.0 → 2.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6e2a6b63db25d81b062d933b0f9db3ba46e9f858869c3a3d2d3274ab1f8a8666
-  data.tar.gz: a8821b81e6d853f588245792739b362ed10ed18bc64b56650e1ec0c923387867
+  metadata.gz: 8226b953bb261edbc90d400904894586076a26aac783653f081940ad04395ba9
+  data.tar.gz: 40961382d8a353a3cae419938c8d11442ea09936d4ae42271db4d03ab4719a84
 SHA512:
-  metadata.gz: 9877b9317ef9dbda4a6c1c0806660276c6273a079cfe61206194dfc651b8b7dea7b33afc2a773c58fa2df70654b428f6da74c43e34e74b687b8fedc250cd7faa
-  data.tar.gz: 57c47323728e63b50c0a3d1530b3e6e3d99c39eb295838871cd57185652a62b017ab88579ddd291d8d38093bd2f46e0c636e3cc4beffb9478b6fa4136e877536
+  metadata.gz: 38a18db6f3d1791b4af486c486cee70844dc950bbe7b8aad519ef0535988279458eb61309c80a1a2e0df9a9d2d7ab54e2b87d6c6239d356d648b03636a9e068b
+  data.tar.gz: 3a6f27b22f0b5aad7586e6d17477f50b9e697dbb6b5ffd1ddcd04ba989abde8f8956588f03f5e5938ef8536e7479648ef79cf305770b9095ad208693fdf9d43d

data/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,28 @@
+---
+name: Bug Report
+about: Create a bug report to help us improve rspec_n
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+## Describe the bug
+
+<!-- Describe the bug clearly and concisely. -->
+
+## To Reproduce
+
+<!-- List the exact steps that can reproduce the behavior. -->
+
+## Expected Behavior
+
+<!-- Explain the behavior you expected. -->
+
+## Screenshots
+
+<!-- Add screenshots if you have any. -->
+
+## Additional Info
+
+<!-- Provide other info that might help. -->

data/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,21 @@
+---
+name: Feature Request
+about: Suggest a new feature
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+## Description
+
+<!-- Provide a clear and concise description of the feature you would like. -->
+<!-- If it's related to a problem or frustration, please tell us about it. -->
+
+## Alternatives
+
+<!-- Describe alternative ideas or solutions you've considered. -->
+
+## Additional Info
+
+<!-- Provide other info or screenshots that might help. -->

data/.github/ISSUE_TEMPLATE/security_issue.md

@@ -0,0 +1,26 @@
+---
+name: Security Issue
+about: Tell us about a security issue
+title: ''
+labels: security
+assignees: ''
+
+---
+
+## Overview
+
+<!-- If you would prefer to submit a private issue, use: -->
+<!--   https://github.com/roberts1000/rspec_n/security/advisories/new -->
+<!-- Otherwise, provide a clear and concise description of what the security issue is. -->
+
+## Proof of Concept (PoC)
+
+<!-- If you have example of how the security issue can be exploited, provide details here. -->
+
+## Screenshots
+
+<!-- If you have screenshots, place them here. -->
+
+## Additional Info
+
+<!-- Place any other info about the problem here. -->

data/.github/pull_request_template.md

@@ -1,3 +1,11 @@
-<!-- Replace XYZ with the related GitHub issue number -->
+## Supported Issue
+
+<!-- Replace `XYZ` with the single associated GitHub issue number. -->
 
 Closes #XYZ
+
+## Additional Info
+
+<!-- Provide details that will help the reviewers understand your work. -->
+
+None

data/.github/workflows/check_pull_request.yml

@@ -1,6 +1,9 @@
 # This workflow will download prebuilt Ruby versions, install dependencies and run checks against Pull Requests.
 
 name: Check Pull Request
+permissions:
+  contents: read
+  pull-requests: write
 on:
   pull_request:
     branches: [ master ]
@@ -13,7 +16,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        ruby-version: ['3.0', '3.1', '3.2', '3.3']
+        ruby-version: ['3.3', '3.4', '4.0']
     steps:
       - uses: actions/checkout@v2
       - name: Set up Ruby
@@ -30,7 +33,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        ruby-version: ['3.0']
+        ruby-version: ['3.3']
     steps:
       - uses: actions/checkout@v2
       - name: Set up Ruby

data/.rubocop.yml

@@ -12,7 +12,7 @@ inherit_gem:
 # do not attempt to merge these settings with their defaults. Long term changes should be ported to the rubocop_plus gem.
 
 AllCops:
-  TargetRubyVersion: 3.0
+  TargetRubyVersion: 3.3
 
 Style/Documentation:
   Enabled: false

data/CHANGELOG.md

@@ -2,6 +2,17 @@
 
 Issues are tracked at https://github.com/roberts1000/rspec_n/issues. Issues marked as **(Internal)** only affect development.
 
+## 2.1.0 (Jun 07, 2026)
+
+1. [#124](../../issues/124): Remove Ruby 3.0 support.
+1. [#126](../../issues/126): Update development and test gems. **(Internal)**
+1. [#128](../../issues/128): Add Ruby 3.4 support.
+1. [#131](../../issues/131): Remove Ruby 3.1 support.
+1. [#136](../../issues/136): Allow Bundler >= 2.0. **(Internal)**
+1. [#139](../../issues/139): Remove Ruby 3.2 support.
+1. [#141](../../issues/141): Add Ruby 4.0 support.
+1. [#151](../../issues/151): Add workflow permissions. **(Internal)**
+
 ## 2.0.0 (Mar 08, 2024)
 
 1. [#118](../../issues/118): Use `db:schema:load` to prepare databases instead of `db:migrate`.

data/CONTRIBUTING.md

@@ -0,0 +1,8 @@
+# CONTRIBUTING
+
+Contributions are welcome. Please us the following process when submitting work:
+
+1. Create an issue on the [issue page](https://github.com/roberts1000/rspec_n/issues) that targets a **single** problem/enhancement. All PRs should be tied to an issue.
+1. Fork the project.
+1. Create a branch. The name of the branch should start with the issue number that the branch will address.
+1. Submit the PR (and add the requested information in the PR template).

data/Gemfile

@@ -8,8 +8,8 @@ group :development do
 end
 
 group :develoment, :test do
-  gem 'bundler', '~> 2.0'
-  gem 'pry', '~> 0.14.0'
+  gem 'bundler', '>= 2.0'
+  gem 'pry', '~> 0.16.0'
   gem 'rake', '~> 13.0'
   gem 'rspec', '~> 3.0'
 end

data/README.md

@@ -4,15 +4,6 @@ rspec_n is a Ruby gem that makes it easy to run a project's RSpec test suite N t
 
 ![example](https://user-images.githubusercontent.com/2053901/53691471-c6956880-3d4c-11e9-8248-68bbb4c24786.png)
 
-#### Automatic Command Selection
-
-rspec_n inspects files in your project and determines the best way to start RSpec. If it can't make an educated guess, it will use `bundle exec rspec` as the base command and add any extra information you've entered on the command line (like the order or paths). The following is a list of project types that rspec_n can identify and the associated commands it will try to execute:
-
-1. Ruby on Rails Applications: `DISABLE_DATABASE_ENVIRONMENT_CHECK=1 RAILS_ENV=test bundle exec rake db:drop db:create db:schema:load && bundle exec rspec`.
-2. Everything else: `bundle exec rspec`.
-
-**Note:** You can override this behavior by using the `-c` option, which lets you specify your own command. See the [Use a Custom Command to Start RSpec](#Use-a-Custom-Command-to-Start-RSpec) section for more info.
-
 ## Versioning Strategy
 
 Releases are versioned using [SemVer 2.0.0](https://semver.org/spec/v2.0.0.html) with the following caveats:
@@ -21,13 +12,13 @@ Releases are versioned using [SemVer 2.0.0](https://semver.org/spec/v2.0.0.html)
 
 ## Supported Ruby Versions
 
-Ruby 3.0+ is supported.
+Ruby 3.3, 3.4 and 4.0 are supported.
 
 ## Installation
 
 Install by executing:
 
-    $ gem install rspec_n
+    gem install rspec_n
 
 The gem will install an executable called `rspec_n`.
 
@@ -45,128 +36,12 @@ gem 'rspec_n', require: false
 
 ## Usage
 
-### Considerations
-
-#### Ruby on Rails
-
-1. By default, rspec_n will attempt to prepare the test database by executing the following code **before each run**:
-
-    ```
-    DISABLE_DATABASE_ENVIRONMENT_CHECK=1 RAILS_ENV=test bundle exec rake db:drop db:create db:schema:load rake db:drop db:create db:schema:load
-    ```
-    
-    1. `DISABLE_DATABASE_ENVIRONMENT_CHECK=1` disables a Rails check that can prevent the test database from being dropped.
-    1. Since `db:schema:load` is used to prepare the test database, projects must have a correct `schema.rb` or `structure.sql`.
-1. By default, rspec_n tries to ensure an empty database **before each run** so it does not load seed files. If your test suite depends on seeded data, or other special setup, you will need to specify the exact command that rspec_n uses to invoke each run. See the [Use a Custom Command to Start RSpec](#Use-a-Custom-Command-to-Start-RSpec) section for more info.
-
-### Basic Usage
-
-The simplest way to run rspec_n is to give it a positive integer which tells it how many times to run RSpec:
-
-    $ rspec_n 5
-
-As iterations complete, summary output is sent to the screen and detailed output is written to files (in the project's root).
-
-To target specific specs, provide one or more paths. You can do anything you would normally do when passing paths to RSpec:
-
-    $ rspec_n 5 spec/path/to/something_spec.rb
-    $ rspec_n 5 spec/path/to/folder spec/path/to/some/other/file_spec.rb
-    $ rspec_n 5 spec/path/to/folder
-    $ rspec_n 5 spec/path/to/something_spec.rb:5
-
-By default, `--order rand` is always sent to RSpec to force it to run specs in random order. You can use a `defined` order if you don't want randomness:
-
-    $ rspec_n 5 --order defined
-
-Or, let the RSpec configuration in the project determine the order:
-
-    $ rspec_n 5 --order project
-
-### Use a Custom Command to Start RSpec
-
-Use the `-c` option if you want to specify your own command. The following example deletes the `tmp` folder before starting RSpec:
-
-    $ rspec_n 5 -c 'rm -rf tmp && bundle exec rspec'
-
-There are a couple points to consider:
-
-1. Wrap your entire command in a single or double quoted string.
-1. Use `&&` to create compound commands.
-1. rspec_n was created to help discover flaky test suites so it will add `--order rand` to your custom command (which gets passed to RSpec and causes RSpec to run tests randomly). If you need to change the test order, you must add the `--order defined` or `--order project` options to the control the order like this:
-
-    ```
-    $ rspec_n 5 -c 'rm -rf tmp && bundle exec rspec' --order defined
-    ```
-   
-### Control the File Output
-
-rspec_n writes output to the project's root folder, for each iteration, to files with the iteration number in the name (`rspec_n_iteration.1`, `rspec_n_iteration.2`, etc...). If you want to disable this, add the `--no-file` option to the command.
-
-    $ rspec_n 5 --no-file
-
-**Note:** rspec_n deletes all files matching `rspec_n_iteration.*` when it starts, so be sure to move those files to another location if you want to save them.
-
-### Stop on First Failure
-
-You can tell rspec_n to abort the first time an iteration fails by using the `-s` flag. All remaining iterations are skipped.
-
-### Run Specs in Parallel
-
-rspec_n doesn't directly support running specs in parallel, however, you should be able to use the `-c` option to pass a rspec_n the command you use to run parallel specs.
-
-## Configuration
-
-You can create a `.rspec_n` file in your project's root and add command line options to it. They'll be used if `rspec_n` is run without options. Options are any arguments that start with `-` or `--`. For example, `rspec_n 10` or `rspec_n 10 spec/some_spec.rb` will make rspec_n consider `.rspec_n`, but `rspec_n 10 -c "rm -rf /tmp/* && bundle exec rspec"` won't.
-
-Example file format:
-
-```text
---no-file
--s
---order defined
--c "rm -rf tmp && bundle exec rspec"
-```
-
-The config file can be multi line or single line.
-
-## Understanding the Results
-
-rspec_n uses the `STDOUT`, `STDERR` and `EXIT STATUS` of the `rspec` command to decide if the run passed or failed. The run is considered successful if RSpec returns an `EXIT STATUS` of `0` **regardless of any content in the STDERR stream**. rspec_n considers the run to be a failure if RSpec's `EXIT STATUS` `> 0`.
-
-There are times when `STDERR` has content, even though RSpec returns an `EXIT STATUS` of `0`. This frequently happens with deprecation notices and RSpec itself will pass the test suite in this situation. Also, it's not uncommon for code to write messages to `STDERR` that look like errors, but not actually cause RSpec to fail a spec example. If rspec_n is able to detect this situation, it adds `(Warning)` to the results to indicate there's something extra in the `STDERR` that you might want to investigate.
-
-The results of each run (number of tests, number of failures, etc...) are determined by parsing `STDOUT` and extracting information from the line that says `xyz examples, xyz failures, xyz pending`.
+See the [Usage Guide](https://github.com/roberts1000/rspec_n/wiki/usage-guide).
 
 ## Development
 
-### Setup
-
-Install dependencies:
-
-    $ bin/setup
-
-That's it!
-
-### Run Automated Tests
-
-Run the automated test suite with:
-
-    $ rspec
-
-### Start a Console
-
-Choose one of the following to start a console with the gem loaded:
-
-```bash
-$ bin/console  # for Pry
-$ rake console # for IRB
-```
+See the [Development Guide](https://github.com/roberts1000/rspec_n/wiki/development-guide).
 
 ## Contributing
 
-Contributions are welcome. Please us the following process when submitting work:
-
-1. Create an issue on the [issue page](https://github.com/roberts1000/rspec_n/issues) that targets a single problem/enhancement. All PRs should be tied to an issue.
-1. Fork the project.
-1. Create a branch. The name of the branch should start with the issue number that the branch will address.
-1. Submit the PR. In the PR comment (in the UI), add `Closes #xyz` or `Supports #xyz` where `xyz` is the issue number that the PR addresses. The title of the PR (in the UI) should start with `[PR for #xyz] `.
+See [CONTRIBUTING](https://github.com/roberts1000/rspec_n/blob/master/CONTRIBUTING.md) or [SECURITY](https://github.com/roberts1000/rspec_n/blob/master/SECURITY.md).

data/SECURITY.md

@@ -0,0 +1,15 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 2.1.x   | :white_check_mark: |
+| < 2.0   | :x:                |
+
+## Report a Vulnerability
+
+To report a Security issue:
+
+- (**Preferred Method ⭐**) Submit a private GitHub Advisory using [this form](https://github.com/roberts1000/rspec_n/security/advisories/new), to the maintainers. See [Github Security Advisories](https://docs.github.com/en/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories) for more info.
+- Submit a [GitHub Issue](https://github.com/roberts1000/rspec_n/issues/new?template=security_issue.md).

data/lib/rspec_n/version.rb

@@ -1,3 +1,3 @@
 module RspecN
-  VERSION = "2.0.0".freeze
+  VERSION = "2.1.0".freeze
 end

data/rspec_n.gemspec

@@ -20,8 +20,7 @@ Gem::Specification.new do |spec|
     spec.metadata["source_code_uri"] = "https://github.com/roberts1000/rspec_n"
     spec.metadata["changelog_uri"] = "https://github.com/roberts1000/rspec_n/blob/master/CHANGELOG.md"
   else
-    raise "RubyGems 2.0 or newer is required to protect against " \
-          "public gem pushes."
+    raise "RubyGems 2.0 or newer is required to protect against public gem pushes."
   end
 
   # Specify which files should be added to the gem when it is released.
@@ -32,7 +31,7 @@ Gem::Specification.new do |spec|
   spec.bindir        = "exe"
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.require_paths = ["lib"]
-  spec.required_ruby_version = '>= 3.0'
+  spec.required_ruby_version = ">= 3.3"
 
   spec.add_dependency "colorize", "~> 1.1.0"
   spec.add_dependency "cri", "~> 2.15.3"

metadata

@@ -1,14 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: rspec_n
 version: !ruby/object:Gem::Version
-  version: 2.0.0
+  version: 2.1.0
 platform: ruby
 authors:
 - roberts1000
-autorequire: 
 bindir: exe
 cert_chain: []
-date: 2024-03-09 00:00:00.000000000 Z
+date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: colorize
@@ -46,16 +45,21 @@ executables:
 extensions: []
 extra_rdoc_files: []
 files:
+- ".github/ISSUE_TEMPLATE/bug_report.md"
+- ".github/ISSUE_TEMPLATE/feature_request.md"
+- ".github/ISSUE_TEMPLATE/security_issue.md"
 - ".github/pull_request_template.md"
 - ".github/workflows/check_pull_request.yml"
 - ".gitignore"
 - ".rspec"
 - ".rubocop.yml"
 - CHANGELOG.md
+- CONTRIBUTING.md
 - Gemfile
 - LICENSE.md
 - README.md
 - Rakefile
+- SECURITY.md
 - bin/console
 - bin/setup
 - exe/rspec_n
@@ -80,7 +84,6 @@ metadata:
   homepage_uri: https://github.com/roberts1000/rspec_n
   source_code_uri: https://github.com/roberts1000/rspec_n
   changelog_uri: https://github.com/roberts1000/rspec_n/blob/master/CHANGELOG.md
-post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
@@ -88,15 +91,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '3.0'
+      version: '3.3'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.6
-signing_key: 
+rubygems_version: 4.0.13
 specification_version: 4
 summary: A ruby gem that runs RSpec N times.
 test_files: []