es_cli 0.1.0

data/vendor/bundle/ruby/3.1.0/gems/test-unit-3.6.7/README.md

@@ -0,0 +1,108 @@
+# test-unit
+
+[![Gem Version](https://badge.fury.io/rb/test-unit.png)](http://badge.fury.io/rb/test-unit)
+[![Build Status for Ruby 2.1+](https://github.com/test-unit/test-unit/actions/workflows/test.yml/badge.svg?branch=master)](https://github.com/test-unit/test-unit/actions/workflows/test.yml?query=branch%3Amaster+)
+
+* http://test-unit.github.io/
+* https://github.com/test-unit/test-unit
+
+## Description
+
+An xUnit family unit testing framework for Ruby.
+
+test-unit (Test::Unit) is unit testing framework for Ruby, based on xUnit
+principles. These were originally designed by Kent Beck, creator of extreme
+programming software development methodology, for Smalltalk's SUnit. It allows
+writing tests, checking results and automated testing in Ruby.
+
+test-unit ships as part of Ruby as a bundled gem. To check which version is included, see https://stdgems.org/test-unit/.
+It's only necessary to install the gem if you need a newer version.
+
+test-unit is the original Ruby unit testing library, and is still active.
+It is one of two unit testing libraries bundled with Ruby, the other being [minitest](https://github.com/minitest/minitest).
+
+When deciding which to use, consider:
+
+* test-unit is strict about backwards compatibility. A backwards-incompatible change would be considered a bug.
+* test-unit aims to support old Ruby versions, even if EOL.
+
+## Features
+
+* test-unit 1.2.3 is the original test-unit, taken
+  straight from the ruby distribution. It is being
+  distributed as a gem to allow tool builders to use it as a
+  stand-alone package. (The test framework in ruby is going
+  to radically change very soon).
+
+* test-unit will be improved actively and may break
+  compatibility with test-unit 1.2.3. (We will not hope it
+  if it isn't needed.)
+
+* Some features exist as separated gems like GUI test
+  runner. (Tk, GTK+ and Fox) test-unit-full gem package
+  provides for installing all test-unit related gems
+  easily.
+
+## How To
+
+* [How To](https://github.com/test-unit/test-unit/blob/master/doc/text/how-to.md) (link for GitHub)
+* {file:doc/text/how-to.md How To} (link for YARD)
+
+## Install
+
+<pre>
+% sudo gem install test-unit
+</pre>
+
+If you want to use full test-unit features:
+
+<pre>
+% sudo gem install test-unit-full
+</pre>
+
+## License
+
+This software is distributed under either the terms of new Ruby
+License or BSDL. See the file [COPYING](COPYING).
+
+Exception:
+
+  * lib/test/unit/diff.rb is a triple license of (the new Ruby license
+    or BSDL) and PSF license.
+
+## Authors
+
+### Active
+
+* Kouhei Sutou: The current maintainer
+* Haruka Yoshihara: Data driven test supports.
+
+### Inactive
+
+* Nathaniel Talbott: The original author
+* Ryan Davis: The second maintainer
+
+### Images
+
+* Mayu & Co.: kinotan icons
+
+## Thanks
+
+* Daniel Berger: Suggestions and bug reports.
+* Designing Patterns: Suggestions.
+* Erik Hollensbe: Suggestions and bug reports.
+* Bill Lear: A suggestion.
+* Diego Pettenò: A bug report.
+* Angelo Lakra: A bug report.
+* Mike Pomraning: A bug report.
+* David MARCHALAND: Suggestions and bug reports.
+* Andrew Grimm: A bug report.
+* Champak Ch: A bug report.
+* Florian Frank: A bug report.
+* grafi-tt: Bug fixes and reports.
+* Jeremy Stephens: A bug report.
+* Hans de Graaff: Bug reports.
+* James Mead: A bug report.
+* Marc Seeger (Acquia): A bug report.
+* boutil: A bug report.
+* Vladislav Rassokhin: A bug report.

data/vendor/bundle/ruby/3.1.0/gems/test-unit-3.6.7/Rakefile

@@ -0,0 +1,74 @@
+# -*- ruby -*-
+#
+# Copyright (C) 2008-2024  Sutou Kouhei <kou@clear-code.com>
+
+Encoding.default_internal = "UTF-8" if defined?(Encoding.default_internal)
+
+# TODO: Remove me when we drop Ruby 1.9 support.
+unless "".respond_to?(:b)
+  class String
+    def b
+      dup.force_encoding("ASCII-8BIT")
+    end
+  end
+end
+
+require "erb"
+require "yaml"
+require "rubygems"
+require "rake/clean"
+require "yard"
+require "bundler/gem_helper"
+require "packnga"
+
+task :default => :test
+
+base_dir = File.dirname(__FILE__)
+
+helper = Bundler::GemHelper.new(base_dir)
+def helper.version_tag
+  version
+end
+
+helper.install
+spec = helper.gemspec
+
+document_task = Packnga::DocumentTask.new(spec) do |task|
+  task.original_language = "en"
+  task.translate_languages = ["ja"]
+end
+
+Packnga::ReleaseTask.new(spec) do |task|
+  test_unit_github_io_dir_candidates = [
+    "../../www/test-unit.github.io",
+  ]
+  test_unit_github_io_dir = test_unit_github_io_dir_candidates.find do |dir|
+    File.directory?(dir)
+  end
+  task.index_html_dir = test_unit_github_io_dir
+end
+
+task :test do
+  ruby("test/run-test.rb")
+end
+
+namespace :doc do
+  task :add_permalink do
+    news_md = File.read("doc/text/news.md")
+    applied_permalink = news_md.gsub(/(?<pre>\[GitHub#(?<ref>\d+)\])(?!\()/) do
+      "#{Regexp.last_match[:pre]}(https://github.com/test-unit/test-unit/issues/#{Regexp.last_match[:ref]})"
+    end
+
+    File.write("doc/text/news.md", applied_permalink)
+  end
+end
+
+release_task = Rake.application["release"]
+# We use Trusted Publishing.
+release_task.prerequisites.delete("build")
+release_task.prerequisites.delete("release:rubygem_push")
+release_task_comment = release_task.comment
+if release_task_comment
+  release_task.clear_comments
+  release_task.comment = release_task_comment.gsub(/ and build.*$/, "")
+end

data/vendor/bundle/ruby/3.1.0/gems/test-unit-3.6.7/doc/text/getting-started.md

@@ -0,0 +1,246 @@
+## 1. First step of the `test-unit`
+
+Let's getting start `test-unit`.
+
+This document creates an example gem package called `sample` with the `test-unit` testing framework.
+
+## 2. Install bundler and test-unit.
+
+* First, install the `bundler` gem for generating gem template.
+* Second, install the `test-unit` itself.
+
+~~~
+!!!plain
+gem install bundler
+gem install test-unit
+~~~
+
+The `gem list` command output installed packages.
+You will find the following lines.
+
+~~~
+!!!plain
+gem list
+...
+bundler (1.14.6)
+...
+test-unit (3.2.3)
+~~~
+
+## 3. Create gem template.
+
+Next, create a gem template using `bundler` command.
+This command generates package skeleton with a testing framework.
+However, this command can't generate test templates for `test-unit`.
+
+So, First create gem template with the `minitest` testing framework.
+(It's similar to `unit-test`).
+After that, replace some files for `test-unit`.
+
+The `bundle gem -t minitest sample` command will generate the following files.
+
+~~~
+!!!plain
+.
+|-- Gemfile
+|-- README.md
+|-- Rakefile
+|-- bin
+|   |-- console
+|   `-- setup
+|-- lib
+|   |-- sample
+|   |   `-- version.rb
+|   `-- sample.rb
+|-- sample.gemspec  # <- Modify
+`-- test
+    |-- sample_test.rb # <- Modify
+    `-- test_helper.rb # <- Modify
+~~~
+
+## 4. Edit files for `test-unit`
+
+### 4.1. Edit gemspec
+
+Edit `sample.gemspec` like the below.
+Replace `minitest` line to `test-unit`.
+
+Before
+
+~~~
+!!!ruby
+  spec.add_development_dependency "minitest", "~> 5.0"
+~~~
+
+After
+
+~~~
+!!!ruby
+  spec.add_development_dependency "test-unit", "~> 3.2.3"
+~~~
+
+### 4.2. Edit `test/test_helper.rb`
+
+Next, edit the `test/test_helper.rb` file.
+
+Before
+
+~~~
+!!!ruby
+$LOAD_PATH.unshift File.expand_path('../../lib', __FILE__)
+require 'sample'
+
+require 'minitest/autorun' # <-- Modify this line.
+~~~
+
+After
+
+~~~
+!!!ruby
+$LOAD_PATH.unshift File.expand_path('../../lib', __FILE__)
+require 'sample'
+
+require 'test/unit' # <-- After modification.
+~~~
+
+### 4.3 Rakefile (No edit)
+
+This file doesn't need to modify.
+The output is the below.
+
+~~~
+!!!ruby
+require "bundler/gem_tasks"
+require "rake/testtask"
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << "test"
+  t.libs << "lib"
+  t.test_files = FileList['test/**/*_test.rb']
+end
+
+task :default => :test
+~~~
+
+### 4.4 Edit `test/sample_test.rb`
+
+The bundler generate the file `test/sample_test.rb`.
+This file originally templates for `minitest`.
+
+Let's modify this file for `test-unit`
+
+before
+
+~~~
+!!!ruby
+require 'test_helper'
+
+class SampleTest < Minitest::Test # <- Modify here
+  def test_that_it_has_a_version_number
+    refute_nil ::Sample::VERSION
+  end
+
+  def test_it_does_something_useful
+    assert false
+  end
+end
+~~~
+
+After
+
+~~~
+!!!ruby
+require 'test_helper'
+
+class SampleTest < Test::Unit::TestCase # <- After modification
+  def test_that_it_has_a_version_number
+    refute_nil ::Sample::VERSION
+  end
+
+  def test_it_does_something_useful
+    assert false
+  end
+end
+~~~
+
+## 5. Execute test.
+
+The `rake test` command execute test scenarios in the `test` directory.
+Now it tries to two tests. One will success the other one fails.
+
+~~~
+!!!plain
+rake test
+Loaded suite
+/path/to/ruby/lib/ruby/gems/2.3.0/gems/rake-12.0.0/lib/rake/rake_test_loader
+Started
+F
+================================================================================
+Failure: <false> is not true.
+test_it_does_something_useful(SampleTest)
+/path/to/sample/test/sample_test.rb:9:in `test_it_does_something_useful'
+      6:   end
+      7:
+      8:   def test_it_does_something_useful
+  =>  9:     assert false
+     10:   end
+     11: end
+================================================================================
+.
+
+Finished in 0.011521 seconds.
+--------------------------------------------------------------------------------
+2 tests, 2 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
+50% passed
+--------------------------------------------------------------------------------
+173.60 tests/s, 173.60 assertions/s
+rake aborted!
+Command failed with status (1)
+
+Tasks: TOP => test
+(See full trace by running task with --trace)
+~~~
+
+## 6. Create original tests.
+
+Let's create your original tests with the following rules.
+
+* Create a test file in the `test` directory.
+* The file needs suffix  `xxx_test.rb`.
+* You can put test file into the subdirectory like `test/sub`.
+
+Example directory layout.
+
+~~~
+!!!plain
+test
+|-- sample_test.rb
+|-- sub
+|   `-- sample2_test.rb
+`-- test_helper.rb
+~~~
+
+Example test file in the sub directory.
+
+~~~
+!!!ruby
+require 'test_helper'
+
+module Sub
+  class Sample2Test < Test::Unit::TestCase
+    def test_that_it_has_a_version_number
+      refute_nil ::Sample::VERSION
+    end
+
+    def test_it_does_something_useful
+      assert false
+    end
+  end
+end
+~~~
+
+## 7. For more information
+
+Let's read the official document.
+
+* [test-unit](https://test-unit.github.io/index.html)

data/vendor/bundle/ruby/3.1.0/gems/test-unit-3.6.7/doc/text/how-to.md

@@ -0,0 +1,90 @@
+# How To
+
+## Run all tests
+
+To make it easy to run all your tests, you can add a `run_test.rb` script
+to your `test` directory. A simple example might look like:
+
+    base_dir = File.expand_path(File.join(File.dirname(__FILE__), ".."))
+    lib_dir  = File.join(base_dir, "lib")
+    test_dir = File.join(base_dir, "test")
+
+    $LOAD_PATH.unshift(lib_dir)
+
+    require 'test/unit'
+
+    exit Test::Unit::AutoRunner.run(true, test_dir)
+
+Then it's easy to run tests via the command line with,
+
+    $ ruby test/run_test.rb
+
+## Change test runner via the command line
+
+The output format can be changed via the command line with
+the `--runner` option. Simply tack it to the end:
+
+    ruby test/run_test.rb --runner tap
+
+
+## Configure test-unit per-project
+
+Test::Unit reads `test-unit.yml` or `.test-unit.yml` in the current working
+directory as Test::Unit's configuration file. It can contain the following
+settings:
+
+* color scheme definitions
+* test runner to be used
+* test runner options
+* test collector to be used
+
+Except color scheme definitions, all of them can be specified by command
+line option.
+
+Here are sample color scheme definitions:
+
+    color_schemes:
+      inverted:
+        success:
+          name: red
+          bold: true
+        failure:
+          name: green
+          bold: true
+      other_scheme:
+        ...
+
+Here are the syntax of color scheme definitions:
+
+    color_schemes:
+      SCHEME_NAME:
+        EVENT_NAME:
+          name: COLOR_NAME
+          intensity: BOOLEAN
+          bold: BOOLEAN
+          italic: BOOLEAN
+          underline: BOOLEAN
+        ...
+      ...
+
+| Definition  | Description                  |
+|-------------|------------------------------|
+| SCHEME_NAME | the name of the color scheme |
+| EVENT_NAME  | success, failure, pending, omission, notification, error |
+| COLOR_NAME  | black, red, green, yellow, blue, magenta, cyan, white    |
+| BOOLEAN     | true or false |
+
+You can use the above 'inverted' color scheme with the following configuration:
+
+    runner: console
+    console_options:
+      color_scheme: inverted
+    color_schemes:
+      inverted:
+        success:
+          name: red
+          bold: true
+        failure:
+          name: green
+          bold: true
+