piko-max-mod 0.0.1

data/test-unit-3.7.8/doc/text/getting-started.md

@@ -0,0 +1,120 @@
+## 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 (2.6.3, default: 2.6.2)
+...
+test-unit (3.6.8, 3.6.7)
+~~~
+
+## 3. Create gem template.
+
+Next, create a gem template using `bundler` command.
+This command generates package skeleton with a testing framework.
+
+The `bundle gem -t test-unit sample` command will generate a gem template with the `test-unit` testing framework.
+
+## 4. 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/3.4.0/gems/rake-13.2.1/lib/rake/rake_test_loader
+Started
+F
+================================================================================
+Failure: test: something useful(SampleTest)
+/path/to/sample/test/sample_test.rb:13:in 'block in <class:SampleTest>'
+     10:   end
+     11:
+     12:   test "something useful" do
+  => 13:     assert_equal("expected", "actual")
+     14:   end
+     15: end
+<"expected"> expected but was
+<"actual">
+
+diff:
+? expected
+? a     ual
+? ????     ??
+================================================================================
+Finished in 0.013737 seconds.
+--------------------------------------------------------------------------------
+2 tests, 2 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
+50% passed
+--------------------------------------------------------------------------------
+145.59 tests/s, 145.59 assertions/s
+rake aborted!
+Command failed with status (1)
+
+Tasks: TOP => test
+(See full trace by running task with --trace)
+~~~
+
+## 5. 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
+~~~
+
+## 6. For more information
+
+Let's read the official document.
+
+* [test-unit](https://test-unit.github.io/index.html)

data/test-unit-3.7.8/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.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.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.rb --runner emacs
+
+
+## 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
+