rspec_n 1.2.2 → 1.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: d086a277cdeda572b3358f254048ed4e7efa7028
-  data.tar.gz: b17c3463cece7279db187d9469c3ec280efe605b
+SHA256:
+  metadata.gz: 0d531fc0cb07d13bf1700f6809c0566cc72dfe887af684b5493821a1d60e0956
+  data.tar.gz: 6bfe142183b285877bb067b1049bcc02139050d69ea123352904db52b34cfce7
 SHA512:
-  metadata.gz: 3717ceab5cd0fe798eddacebcfc66ad1ceccad082bec1c15f0843ced97179df37ceff80d24c8ff0fc47b2079408d5ec02eebbae41746fe044212e35dc8a4c9e7
-  data.tar.gz: 2f2b6d24ee1e683dd312554560e0c1af09aae7da2f3dd81741fa24ea939b66c66792720463d6fd0517c4ac8b9ac1c8c4446c2b741c4828ab2496674f3516ec31
+  metadata.gz: ab882b6d984ef3565d26c4d72357802a6daf058374c175e10b267f1bfcfb825e50f4ddcbda66d96dbebadeeecee7d4ac2f4c89d53276b217804436adbc300ef6
+  data.tar.gz: 681e5b4f42152b285174535231ef0d07054fefa57c9fcbabdc1e23ad466ebcf3d8e84dd5829afd8b91db733636fd9d6e50b5d4986d99493b17122a6406a8092b

data/.github/workflows/check_pull_request.yml

@@ -0,0 +1,54 @@
+# This workflow will download prebuilt Ruby versions, install dependencies and run checks against Pull Requests.
+
+name: Check Pull Request
+on:
+  pull_request:
+    branches: [ master ]
+env:
+  # The pull request can have less than, or equal to, this number of rubocop issues and pass.
+  RUBOCOP_ISSUE_THRESHOLD: 5
+jobs:
+  rspec:
+    name: Run RSpec
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        ruby-version: ['2.7', '3.0', '3.1']
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Ruby
+        # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby,
+        # change this to (see https://github.com/ruby/setup-ruby#versioning):
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby-version }}
+          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
+      - name: Execute rspec command
+        run: bundle exec rspec
+  rubocop:
+    name: Run Rubocop
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        ruby-version: ['2.7']
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Ruby
+        # To automatically get bug fixes and new Ruby versions for ruby/setup-ruby,
+        # change this to (see https://github.com/ruby/setup-ruby#versioning):
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby-version }}
+          bundler-cache: true # runs 'bundle install' and caches installed gems automatically
+      - name: Execute rubo command
+        run: bundle exec rubo
+      - name: Evaluate rubo threshold
+        run: |
+          count=$(cat rubocop/total-violations-count.txt)
+          if [[ "$count" -gt $RUBOCOP_ISSUE_THRESHOLD ]]; then
+              echo "Failure: Found $count RuboCop issue(s). It must have $RUBOCOP_ISSUE_THRESHOLD or less. \
+          Run 'rubo' and resolve the issues listed in rubocop/style-issues.html"
+              exit 1
+          else
+              echo "Success: Found $count RuboCop issue(s), which is less than the limit of $RUBOCOP_ISSUE_THRESHOLD"
+          fi

data/.gitignore

@@ -11,3 +11,5 @@
 # rspec failure tracking
 .rspec_status
 Gemfile.lock
+
+rspec_n_iteration.*

data/.rubocop.yml

@@ -1,8 +1,21 @@
+# DO NOT MODIFY THIS FILE unless you want to deviate from the rubocop_plus ruleset.
+
+# This file defines the settings used by rubocop when it runs. You would normally add your customizations directly to this
+# file, but this file has been pre configured to read settings out of the rubocop_plus gem instead.
+
+# Tell rubocop to load its settings from the rubocop_plus gem.
+
 inherit_gem:
   rubocop_plus: config/rubocop.yml
 
+# Place custom settings below this comment. All customizations will OVERRIDE rubocop_plus rules. rubocop_plus & rubocop
+# do not attempt to merge these settings with their defaults. Long term changes should be ported to the rubocop_plus gem.
+
 AllCops:
-  TargetRubyVersion: 2.3
+  TargetRubyVersion: 2.7
 
 Style/Documentation:
   Enabled: false
+
+Rails:
+  Enabled: false

data/CHANGELOG.md

@@ -1,29 +1,52 @@
 # CHANGELOG
 
-## Next Release
+Issues are tracked at https://github.com/roberts1000/rspec_n/issues. Issues marked as **(Internal)** only affect development.
 
-1. (New) Add Gemfile usage instructions to the README. ([Issue #36](https://github.com/roberts1000/rspec_n/issues/36))
-1. (New) Remove locking to a specify version of Ruby in development. ([Issue #41](https://github.com/roberts1000/rspec_n/issues/41))
-1. (New) Use pry 0.12.x for development. ([Issue #43](https://github.com/roberts1000/rspec_n/issues/43))
-1. (New) Stop `--order rand` from being added to the final command when a custom order is specified. ([Issue #38](https://github.com/roberts1000/rspec_n/issues/38))
+## 1.5.0 (Aug 28, 2022)
+
+1. [#87](../../issues/87): Add GitHub action workflow to check pull requests. **(Internal)**
+1. [#93](../../issues/93): Make Ruby 2.7.0 the min supported Ruby.
+1. [#97](../../issues/97): Add Ruby 3.1 support.
+
+## 1.4.0 (May 16, 2021)
+
+1. [#64](../../issues/64): Use `pry` `~> 0.14.0`. **(Internal)**
+1. [#66](../../issues/66): Update ruby & bundler versions in `.travis.yml`. **(Internal)**
+1. [#68](../../issues/68): Make Ruby 2.6.0 the minimum supported version.
+1. [#73](../../issues/73): Use `rake` `~> 13.0`. **(Internal)**
+1. [#78](../../issues/78): Require `Pathname`.
+1. [#83](../../issues/83): Use `rubocop_plus` `~> 2.0`. **(Internal)**
+
+## 1.3.0 (Jan 13, 2020)
+
+1. [#49](../../issues/49): Make `--order project` work.
+1. [#55](../../issues/55): Add `--dir` and `--timestamp` output options.
+1. [#57](../../issues/57): Redesign the `CHANGELOG.md`.
+
+## 1.2.2 (Jun 22, 2019)
+
+1. [#36](../../issues/36): Add instructions for installing `rspec_n` in project Gemfiles.
+1. [#38](../../issues/38): Stop `--order rand` from being added to the final command when a custom order is specified.
+1. [#41](../../issues/41): Remove locking to a specify version of Ruby in development. **(Internal)**
+1. [#43](../../issues/43): Use `pry` `0.12.x` for development. **(Internal)**
 
 ## 1.2.1 (Mar 06, 2019)
 
-1. (Fix) Make `-v` and `--version` work again. ([Issue #30](https://github.com/roberts1000/rspec_n/issues/30))
+1. [#30](../../issues/30): Make `-v` and `--version` work again.
 
 ## 1.2.0 (Mar 03, 2019)
 
-1. (New) Write the command that was used to run rspec_n to the output files. ([Issue #26](https://github.com/roberts1000/rspec_n/issues/26))
+1. [#26](../../issues/26): Write the command that was used to run rspec_n to the output files.
 
 ## 1.1.0 (Mar 03, 2019)
 
-1. (New) Add **Result Counts** column which shows the result counts for each run (e.g. "400 examples, 2 failures, 3 pending"). ([Issue #19](https://github.com/roberts1000/rspec_n/issues/19))
-1. (New) Allow an optional path argument, that is passed to RSpec, to target specs (e.g. `rspec_n 3 spec/features/example_spec.rb`, `rspec_n spec/features/example_spec.rb:5`, `rspec_n spec/features 4`). ([Issue #20](https://github.com/roberts1000/rspec_n/issues/20))
-1. (New) Rename the `Result Counts` column to `Results` and remove the existing `Results` column. ([Issue #23](https://github.com/roberts1000/rspec_n/issues/23))
+1. [#19](../../issues/19): Add **Result Counts** column which shows the result counts for each run (e.g. "400 examples, 2 failures, 3 pending").
+1. [#20](../../issues/20): Accept an optional path argument, that is passed to RSpec, to target specs (e.g. `rspec_n 3 spec/features/example_spec.rb`, `rspec_n spec/features/example_spec.rb:5`, `rspec_n spec/features 4`).
+1. [#23](../../issues/23): Rename the `Result Counts` column to `Results` and remove the existing `Results` column.
 
 ## 1.0.0 (Feb 18, 2019)
 
-1. (New) Add initial core logic. ([Issue #1](https://github.com/roberts1000/rspec_n/issues/1))
-1. (New) Add initial CLI. ([Issue #4](https://github.com/roberts1000/rspec_n/issues/4))
-1. (New) Write results of each iteration to a separate file. ([Issue #5](https://github.com/roberts1000/rspec_n/issues/5))
-1. (New) Add `-s` option to stop on first failure. ([Issue #6](https://github.com/roberts1000/rspec_n/issues/6))
+1. [#1](../../issues/1): Add initial core logic.
+1. [#4](../../issues/4): Add initial CLI.
+1. [#5](../../issues/5): Write results of each iteration to a separate file.
+1. [#6](../../issues/6): Add `-s` option to stop on first failure.

data/Gemfile

@@ -4,5 +4,5 @@ source "https://rubygems.org"
 gemspec
 
 group :development do
-  gem 'rubocop_plus', "~> 1.0", require: false
+  gem 'rubocop_plus', '~> 2.0', require: false
 end

data/LICENSE.md

@@ -1,6 +1,6 @@
-The MIT License (MIT)
+MIT License
 
-Copyright (c) 2019 roberts1000
+Copyright (c) 2021 roberts1000
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -9,13 +9,13 @@ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 copies of the Software, and to permit persons to whom the Software is
 furnished to do so, subject to the following conditions:
 
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
 
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.md

@@ -1,32 +1,38 @@
 # rspec_n
 
-rspec_n is a Ruby gem that makes it easy to run a project's RSpec test suite N times.  You can customize the command that is used to start RSpec, or let rspec_n guess the best command (based on the files in your project).  rspec_n is useful for finding repeatability or flakiness issues in automated test suites.
+rspec_n is a Ruby gem that makes it easy to run a project's RSpec test suite N times. You can customize the command that is used to start RSpec, or let rspec_n guess the best command (based on the files in your project). rspec_n is useful for finding repeatability issues in RSpec test suites.
 
 ![example](https://user-images.githubusercontent.com/2053901/53691471-c6956880-3d4c-11e9-8248-68bbb4c24786.png)
 
-## Version Strategy
+## Versioning Strategy
 
-Releases are versioned using [semver 2.0.0](https://semver.org/spec/v2.0.0.html).
+Releases are versioned using [SemVer 2.0.0](https://semver.org/spec/v2.0.0.html) with the following caveats:
 
-## Supported Rubies
+1. Support for Ruby versions, that reach EOL, can be removed in a major **or** minor release.
 
-Ruby 2.3.0+ is supported.
+## Supported Ruby Versions
+
+Ruby 2.7, 3.0 and 3.1.
 
 ## Installation
 
-Install by executing
+Install by executing:
 
     $ gem install rspec_n
 
-The gem will install an exectuable called `rspec_n` on your system.  You may also want to add `rspec_n_iteration.*` to your `.gitignore` to exclude the output generated by rspec_n from your project's repo.
+The gem will install an executable called `rspec_n`.
+
+Add the following to your project's `.gitignore` to exclude the output generated by rspec_n from your project's repo:
+
+    rspec_n_iteration.*
 
-#### Using in a Gemfile
+#### Usage in a Gemfile
 
-If you want to add rspec_n to your Gemfile, make sure you use the `require: false` option so rspec_n files aren't loaded into your application.  rspec_n doesn't provide any runtime benefit to an app and requiring it will add unnecessary code to your project.  Also, rspec_n is designed as a standalone commandline tool and isn't tested for compatibility inside other apps.
+If you add rspec_n to your Gemfile, use the `require: false` option so rspec_n isn't loaded into your app. rspec_n doesn't provide any runtime benefit to apps and requiring it will add unnecessary code to your project. Also, rspec_n is designed as a standalone commandline tool and isn't tested for compatibility inside other apps.
 
-    ```ruby
-    gem 'rspec_n', require: false
-    ```
+```ruby
+gem 'rspec_n', require: false
+```
 
 ## Usage
 
@@ -34,70 +40,107 @@ The simplest way to run rspec_n is to give it a positive integer which tells it
 
     $ rspec_n 5
 
-As each iteration completes, output will be sent to the screen and dumped to a file.  If you need to examine the detailed output of a run, it is available in the output files.
+As iterations complete, summary output is sent to the screen and detailed output is written to files (in the project's root).
 
-You can also list one or more paths to target specs.  You can do anything you would normally do when giving RSpec paths:
+To target specific specs, provide one or more paths. You can do anything you would normally do when giving 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 sent to RSpec to force it to run specs in random order.  You can use a `defined` order if you don't want randomness:
+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 configuration files in the project determine the order:
+Or, let the RSpec configuration in the project determine the order:
 
     $ rspec_n 5 --order project
 
+#### Config file
+
+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:
+
+```
+--no-file
+-s
+--order defined
+-c "rm -rf tmp && bundle exec rspec"
+```
+
+The config file can be multi line or single line.
+
 #### Automatic Command Selection
 
-rspec_n will inspect the files in your project and pick 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:
+rspec_n inspects files in your project so it can pick 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:migrate && bundle exec rspec`.
 2. Everything else: `bundle exec rspec`.
 
-#### Use Custom Command to Start RSpec
+#### Use a Custom Command to Start RSpec
 
-If you don't want rspec_n to automatically pick the best command, you can use the `-c` option and specify a command.  The following example deletes the `tmp` folder before starting 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 couple points to consider:
+There are a couple points to consider:
 
-1. Wrap your entire command in a single or double quoted string so rspec_n can acturately determine the command.
-1. You can use the `&&` operator to join commands.
-1. rspec_n was partially created to help discover flaky test suites so it will add `--order rand` to a custom command even if don't specify the order.  You must explicitly use `--order defined` or `--order project` if you want something else.
+1. Wrap your entire command in a single or double quoted string.
+1. Use `&&` to create compound commands.
+1. Avoid trying to change test order within a custom command. rspec_n was created to help discover flaky test suites so it adds `--order rand` to your custom command. Use the `--order defined` or `--order project` options to the control the order. 
 
 #### Control File Output
 
-rspec_n writes output for each iteration in a sequence of files `rspec_n_iteration.1`, `rspec_n_iteration.2`, etc...  This saves you from having to rerun your test suite when you find a particular seed that causes your test suite to fail.  If you want to disable this, add the `--no-file` option to the command.
+rspec_n writes output for each iteration to files with the iteration number (`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 tomove those files to another location if you want to save them.
+**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.  Any remaining iterations will be skipped.
+You can tell rspec_n to abort the first time an iteration fails by using the `-s` flag. All remaining iterations are skipped.
 
 ## Understanding the Results
 
-rspec_n uses the STDOUT, STDERR and EXIT STATUS of the `rspec` command  to figure out what to show in the **Results** column.  The general results are determined by finding the line in RSpec's STDOUT that says `xyz examples, xyz failures, xyz pending`.  rspec_n considers the run to be successful if RSpec returns an EXIT STATUS of 0 **regardless of any content in the STDERR stream**; it considers the run to be a failure if RSpec's EXIT STATUS > 0.
+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.
 
-There are times when RSpec's STDERR might have content, even though it returns an EXIT STATUS of 0. This frequently happens with deprecation notices and RSpec itself will pass the test suite in this situation. Unfortunately, it's not uncommon for code to write messages that look like errors to STDERR, but not actually raise an error and cause RSpec to fail a spec example.  rspec_n reports this situation by adding a `(Warning)` label 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`.
 
 ## Development
 
-After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for a Pry console, or `rake console` for an IRB console, that will allow you to experiment.
+### Setup
 
-To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+Install dependencies:
 
-## Contributing
+    $ bin/setup
+
+That's it!
+
+### Run Automated Tests
+
+Run the automated test suite with:
+
+    $ rspec
 
-Bug reports and pull requests are welcome on GitHub at https://github.com/roberts1000/rspec_n.
+### 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
+```
+
+## Contributing
 
-## License
+Contributions are welcome. Please us the following process when submitting work:
 
-The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+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] `.

data/Rakefile

@@ -5,7 +5,8 @@ RSpec::Core::RakeTask.new(:spec)
 
 task :default => :spec
 
+desc "Start an irb console"
 task :console do
-  # exec "pry -r rspec_n -I ./lib"
-  exec "irb -r rspec_n -I ./lib"
+  exec "pry -r rspec_n -I ./lib"
+  # exec "irb -r rspec_n -I ./lib"
 end

data/bin/console

@@ -6,8 +6,7 @@ require "rspec_n"
 # You can add fixtures and/or initialization code here to make experimenting
 # with your gem easier. You can also use a different console, if you like.
 
-require "pry"
-Pry.start
+# Run 'rake console' to start a pry console.
 
-# require "irb"
-# IRB.start(__FILE__)
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -4,5 +4,3 @@ IFS=$'\n\t'
 set -vx
 
 bundle install
-
-# Do any other automated setup that you need to do here

data/exe/rspec_n

@@ -15,19 +15,21 @@ lib = File.expand_path('../lib', __dir__)
 $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 
 require "cri"
+require "fileutils"
 require "rspec_n/version"
 require "rspec_n/constants"
+require "rspec_n/helpers/arguments_helper"
 require "rspec_n/errors/bad_option"
 
 # rubocop:disable Metrics/BlockLength
 command = Cri::Command.define do
   usage       'rspec_n [iterations] [options]'
   description "rspec_n is an executable installed by the rspec_n Ruby gem.  It provides a " \
-    "way to re-run an RSpec test suite 'N' times, which is useful when determining " \
-    "if a test suite is consistent.\n\n" \
-    "STATUS CODES\n\n" \
-    "0 - rspec_n ran successfully                                            \u00A0\n" \
-    "1 - problem with the commandline options                                \u00A0"
+              "way to re-run an RSpec test suite 'N' times, which is useful when determining " \
+              "if a test suite is consistent.\n\n" \
+              "STATUS CODES\n\n" \
+              "0 - rspec_n ran successfully                                            \u00A0\n" \
+              "1 - problem with the commandline options                                \u00A0"
 
   flag :h, :help, 'show help' do |_value, cmd|
     puts cmd.help
@@ -35,12 +37,19 @@ command = Cri::Command.define do
   end
 
   command_description = "By default, rspec_n will guess the best command to run RSpec; " \
-    "override it by setting a custom command; wrap the entire command in single or double quotes; " \
-    "join multiple commands with '&&'"
+                        "override it by setting a custom command; wrap the entire command in single or double quotes; " \
+                        "join multiple commands with '&&'"
   option :c, :command, command_description, argument: :required
 
   flag nil, "no-file", "Do not write iteration output to files"
 
+  flag nil, "timestamp", "Write iteration output to a timestamped directory, which can " \
+                         "prevent accidental loss. NOTE: It is up to the user to periodically clean up files."
+
+  command_description = "Write iteration output to files in the provided directory " \
+                        "rather than the current working directory. Can be used along with the timestamp flag."
+  option :d, :dir, command_description, argument: :required
+
   flag :s, "stop-fast", "Stop when an iteration reports a failure."
 
   command_description =
@@ -63,7 +72,7 @@ end
 # rubocop:enable Metrics/BlockLength
 
 begin
-  command.run(ARGV)
+  command.run(ArgumentsHelper.arguments)
   exit 0
 rescue RspecN::BadOption => e
   warn e.message.colorize(:red)

data/lib/rspec_n/constants.rb

@@ -3,7 +3,7 @@ module RspecN
   DEFAULT_ITERATIONS = 10
   DEFAULT_COMMAND = 'bundle exec rspec'.freeze
   DEFAULT_RSPEC_STARTER_COMMAND = 'bin/start_rspec'.freeze
-  # rubocop:disable Metrics/LineLength
+  # rubocop:disable Layout/LineLength
   DEFAULT_RAILS_COMMAND = 'DISABLE_DATABASE_ENVIRONMENT_CHECK=1 RAILS_ENV=test bundle exec rake db:drop db:create db:migrate && bundle exec rspec'.freeze
-  # rubocop:enable Metrics/LineLength
+  # rubocop:enable Layout/LineLength
 end

data/lib/rspec_n/errors/bad_option.rb

@@ -6,7 +6,7 @@ module RspecN
     end
 
     def message
-      allowed = RspecN::ALLOWED_ORDER_OPTIONS.collect { |val| "'" + val + "'" }
+      allowed = RspecN::ALLOWED_ORDER_OPTIONS.collect { |val| "'#{val}'" }
       "Order must be #{allowed.to_sentence}.  '#{@details}' is not allowed.\n"
     end
   end

data/lib/rspec_n/formatters/file_formatter.rb

@@ -12,16 +12,19 @@ module RspecN
       end
 
       def delete_all_files
-        Dir.glob("#{BASE_FILE_NAME}.**").each { |file| File.delete(file) }
+        log_directory = Pathname.new(@runner.input.log_path)
+        Dir.glob(log_directory.join("#{BASE_FILE_NAME}.**")).each { |file| File.delete(file) }
       end
 
       def write(run, command)
         return if run.skipped?
         return unless @runner.input.write_files?
 
-        file_name = "#{BASE_FILE_NAME}.#{run.iteration}"
+        log_directory = Pathname.new(@runner.input.log_path)
+        FileUtils.mkdir_p(log_directory)
+        file_path = log_directory.join("#{BASE_FILE_NAME}.#{run.iteration}")
 
-        File.open(file_name, "w") do |f|
+        File.open(file_path, "w") do |f|
           f.write("Iteration: #{run.iteration}\n")
           f.write("Start Time: #{run.formatted_start_time(@format)}\n")
           f.write("Finish Time: #{run.formatted_finish_time(@format)}\n")

data/lib/rspec_n/formatters/table_formatter.rb

@@ -62,7 +62,7 @@ module RspecN
       end
 
       def padded_header_column_labels
-        columns.collect { |name, max_width| padded_header_column_label(name, max_width) }.join("")
+        columns.collect { |name, max_width| padded_header_column_label(name, max_width) }.join
       end
 
       def max_column_width_for(name)
@@ -92,10 +92,8 @@ module RspecN
 
       def result_color_symbol(run)
         case run.status_string
-        when "Pass (Warnings)" then :green
-        when "Pass" then :green
+        when "Pass", "Pass (Warnings)" then :green
         when "Fail" then :red
-        when "Skip" then :yellow
         else :yellow
         end
       end

data/lib/rspec_n/helpers/arguments_helper.rb

@@ -0,0 +1,26 @@
+require 'shellwords'
+
+class ArgumentsHelper
+  class << self
+    def arguments
+      if File.exist?(".rspec_n") && no_options_in_arguments?
+        options = read_options_from_file
+        if options.any?
+          print "Reading options from `.rspec_n` file\n"
+          return ARGV + options
+        end
+      end
+      ARGV
+    end
+
+    # Read arguments from the config file only if no arguments are provided by user
+    def no_options_in_arguments?
+      ARGV.grep(/^-/).empty? # Match args that start with - (or --). Those are the options.
+    end
+
+    # Options can be listed on a single line in the config file, or listed on separate lines.
+    def read_options_from_file
+      Shellwords.shellwords File.read(".rspec_n").to_s.gsub(/\n|\r\n/, " ")
+    end
+  end
+end

data/lib/rspec_n/helpers/core_ext/string.rb

@@ -1,7 +1,7 @@
 class String
   # https://stackoverflow.com/questions/39743299/check-if-a-string-contains-only-digits-in-ruby
   def all_digits?
-    self =~ /\A\d+\z/ ? true : false
+    match?(/\A\d+\z/)
   end
 
   def remove_color

data/lib/rspec_n/input.rb

@@ -1,6 +1,7 @@
 module RspecN
   class Input
-    attr_accessor :iterations, :command, :stop_fast, :write_files
+    attr_accessor :iterations, :command, :stop_fast, :write_files, :log_path
+
     def initialize(options, args)
       @args = args
       @unprocessed_args_array = args.entries
@@ -12,6 +13,8 @@ module RspecN
       @command = determine_command
       @stop_fast = options.fetch(:"stop-fast", false)
       @write_files = !options.fetch(:'no-file', false)
+      @timestamp = options.fetch(:timestamp, false)
+      @log_path = determine_log_path
     end
 
     def write_files?
@@ -21,7 +24,8 @@ module RspecN
     private
 
     def validate_order
-      return unless (order = @options.fetch(:order, nil))
+      order = @options.fetch(:order, nil)
+      return unless order
 
       raise BadOption, order unless RspecN::ALLOWED_ORDER_OPTIONS.include?(order)
     end
@@ -43,8 +47,8 @@ module RspecN
 
     def determine_command
       command = @options.fetch(:command, guessed_command)
-      command += " " + @spec_path if @spec_path
-      command += " --order " + @order if should_append_order?(command)
+      command += " #{@spec_path}" if @spec_path
+      command += " --order #{@order}" if should_append_order?(command)
       command
     end
 
@@ -66,7 +70,18 @@ module RspecN
     end
 
     def should_append_order?(command)
-      command.match(/--order/).nil?
+      return false if @order == "project"
+
+      !command.include?("--order")
+    end
+
+    def determine_log_path
+      log_path = Pathname.new(@options.fetch(:dir, Dir.pwd))
+      return log_path unless @timestamp
+
+      directory_name = File.basename($PROGRAM_NAME)
+      directory_name << "-#{Time.now.getlocal.strftime('%Y%m%d%H%M%S%L')}"
+      log_path.join(directory_name)
     end
   end
 end

data/lib/rspec_n/runner.rb

@@ -25,15 +25,15 @@ module RspecN
     end
 
     def total_passed
-      @runs.values.select(&:passed?).size
+      @runs.values.count(&:passed?)
     end
 
     def total_failed
-      @runs.values.select(&:failed?).size
+      @runs.values.count(&:failed?)
     end
 
     def total_skipped
-      @runs.values.select(&:skipped?).size
+      @runs.values.count(&:skipped?)
     end
 
     private

data/lib/rspec_n/version.rb

@@ -1,3 +1,3 @@
 module RspecN
-  VERSION = "1.2.2".freeze
+  VERSION = "1.5.0".freeze
 end

data/lib/rspec_n.rb

@@ -3,6 +3,7 @@ require "rspec_n/version"
 require "colorize"
 require "cri"
 require "open3"
+require "pathname"
 
 require "rspec_n/helpers/time_helpers"
 require "rspec_n/helpers/core_ext/array"
@@ -20,9 +21,9 @@ require "rspec_n/formatters/table_formatter"
 # Setup pry for development when running "rake console". Guard against load
 # errors in production (since pry is only loaded as a DEVELOPMENT dependency
 # in the .gemspec)
-# rubocop:disable Lint/HandleExceptions
+# rubocop:disable Lint/SuppressedException
 begin
   require "pry"
 rescue LoadError
 end
-# rubocop:enable Lint/HandleExceptions
+# rubocop:enable Lint/SuppressedException

data/rspec_n.gemspec

@@ -2,7 +2,6 @@ lib = File.expand_path("lib", __dir__)
 $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 require "rspec_n/version"
 
-# rubocop:disable Metrics/BlockLength
 Gem::Specification.new do |spec|
   spec.name          = "rspec_n"
   spec.version       = RspecN::VERSION
@@ -22,7 +21,7 @@ Gem::Specification.new do |spec|
     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."
+          "public gem pushes."
   end
 
   # Specify which files should be added to the gem when it is released.
@@ -33,14 +32,13 @@ 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 = '>= 2.3.0'
+  spec.required_ruby_version = '>= 2.7.0'
 
   spec.add_development_dependency "bundler", "~> 2.0"
-  spec.add_development_dependency "pry", "~> 0.12.0"
-  spec.add_development_dependency "rake", "~> 12.0"
+  spec.add_development_dependency "pry", "~> 0.14.0"
+  spec.add_development_dependency "rake", "~> 13.0"
   spec.add_development_dependency "rspec", "~> 3.0"
 
   spec.add_dependency "colorize", "~> 0.8.0"
   spec.add_dependency "cri", "~> 2.15.3"
 end
-# rubocop:enable Metrics/BlockLength

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: rspec_n
 version: !ruby/object:Gem::Version
-  version: 1.2.2
+  version: 1.5.0
 platform: ruby
 authors:
 - roberts1000
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2019-06-22 00:00:00.000000000 Z
+date: 2022-08-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -30,28 +30,28 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.12.0
+        version: 0.14.0
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.12.0
+        version: 0.14.0
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '12.0'
+        version: '13.0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '12.0'
+        version: '13.0'
 - !ruby/object:Gem::Dependency
   name: rspec
   requirement: !ruby/object:Gem::Requirement
@@ -102,10 +102,10 @@ executables:
 extensions: []
 extra_rdoc_files: []
 files:
+- ".github/workflows/check_pull_request.yml"
 - ".gitignore"
 - ".rspec"
 - ".rubocop.yml"
-- ".travis.yml"
 - CHANGELOG.md
 - Gemfile
 - LICENSE.md
@@ -119,6 +119,7 @@ files:
 - lib/rspec_n/errors/bad_option.rb
 - lib/rspec_n/formatters/file_formatter.rb
 - lib/rspec_n/formatters/table_formatter.rb
+- lib/rspec_n/helpers/arguments_helper.rb
 - lib/rspec_n/helpers/core_ext/array.rb
 - lib/rspec_n/helpers/core_ext/string.rb
 - lib/rspec_n/helpers/time_helpers.rb
@@ -142,15 +143,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 2.3.0
+      version: 2.7.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubyforge_project: 
-rubygems_version: 2.6.14
+rubygems_version: 3.3.20
 signing_key: 
 specification_version: 4
 summary: A ruby gem that runs RSpec N times.

data/.travis.yml

@@ -1,14 +0,0 @@
----
-sudo: false
-language: ruby
-cache: bundler
-rvm:
-  - 2.3.8
-  - 2.4.5
-  - 2.5.5
-  - 2.6.3
-before_install: gem install bundler -v 2.0.2
-notifications:
-  email:
-    on_success: never # default: change
-    on_failure: never # default: always