test-unit 3.3.1 → 3.3.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 93aaef767a30d0882b6048299d858f799ea416bfdccc9daef7d2686b5a913f98
-  data.tar.gz: 00a5b7f5ccfe50603d4d1b926424b3d8336c21b3126e0dc324b17f156a48ef6a
+  metadata.gz: b7aaedb309f50feea0367554eeef8b79f0daf6edb5c75c4b66df9e990c35d371
+  data.tar.gz: 17bd1f32e290087d6b57cf5337dbd8cc8259896671ef1cc6c23b15579e52698b
 SHA512:
-  metadata.gz: a8edd6f065bf74bd4ead4dc49c6a96a635c92cfec4f7089202e658361a715d003b2c0422b58f8e97a84f7fa4ec90b137343e4737ef81741c32cb53c1191c182b
-  data.tar.gz: be3541d1116d75979c82060d17278e40397adc8df4dea96b982fc5b61583749b975d1cdfcfbc634dc1f4045c8d7994575897e38ccc78c785049ea6673d973f67
+  metadata.gz: d86d52e5ed5bc4930f6b26f76d0294cb2e50261f16495649e75eb79ab2631cd23c2bfd6602ede230384f3971e9f780f87a8324ca15a0b3a09866a1c449641e55
+  data.tar.gz: 26975998cc3e8c4c6e5d372b3d3e51316e2709508fdb5ebd87083dcf658941f4b038bcc4f6e1f714ba891a14c1ccbca5ec5e197065a45163dcfd5861cd5b6c15

data/doc/text/news.md

@@ -1,5 +1,72 @@
 # News
 
+## 3.3.6 - 2020-06-10 {#version-3-3-6}
+
+### Improvements
+
+  * `name`, `--ignore-name`:
+
+     * Added support for regular expression options.
+
+     * Added support for matching with class name in exact match mode.
+       [Reported by Jun Aruga]
+
+  * Updated ruby-talk mailing list information
+    [GitHub#168][Patch by Chris Kampmeier]
+
+### Thanks
+
+  * Chris Kampmeier
+
+  * Jun Aruga
+
+## 3.3.5 - 2020-01-10 {#version-3-3-5}
+
+### Improvements
+
+  * Improved code snippet showing with different default external encoding.
+    [GitHub#166][Patch by Yuta Iwama]
+
+### Thanks
+
+  * Yuta Iwama
+
+## 3.3.4 - 2019-09-30 {#version-3-3-4}
+
+### Improvements
+
+  * Converted markup format to Markdown from RDoc.
+    [GitHub#164][Patch by OGAWA KenIchi]
+
+  * test: Stopped to depend on `Time#inspect` format.
+    [GitHub#165][Reported by Benoit Daloze]
+
+### Thanks
+
+  * OGAWA KenIchi
+
+  * Benoit Daloze
+
+## 3.3.3 - 2019-05-10 {#version-3-3-3}
+
+### Fixed
+
+  * Fixed a bug that priority mode with test case name that uses
+    special characters such as `?` can't be used on Windows.
+
+## 3.3.2 - 2019-04-11 {#version-3-3-2}
+
+### Fixes
+
+  * Fixed a bug that `Test::Unit::Collector::Load` doesn't load test
+    files under sub directories when these files have the same base
+    name as test files in upper directories.
+    [Reported by Kenta Murata]
+
+### Thanks
+
+  * Kenta Murata
+
 ## 3.3.1 - 2019-03-27 {#version-3-3-1}
 
 ### Improvements

data/lib/test/unit.rb

@@ -3,10 +3,10 @@ require 'test/unit/autorunner'
 
 module Test # :nodoc:
   #
-  # = Test::Unit - Ruby Unit Testing Framework
-  # 
-  # == Introduction
-  # 
+  # # Test::Unit - Ruby Unit Testing Framework
+  #
+  # ## Introduction
+  #
   # Unit testing is making waves all over the place, largely due to the
   # fact that it is a core practice of XP. While XP is great, unit testing
   # has been around for a long time and has always been a good idea. One
@@ -18,19 +18,19 @@ module Test # :nodoc:
   # as possible, you slowly build up a wall of things that cannot break
   # without you immediately knowing about it. This is when unit testing
   # hits its peak usefulness.
-  # 
+  #
   # Enter Test::Unit, a framework for unit testing in Ruby, helping you to
   # design, debug and evaluate your code by making it easy to write and
   # have tests for it.
-  # 
-  # 
-  # == Notes
-  # 
+  #
+  #
+  # ## Notes
+  #
   # Test::Unit has grown out of and superceded Lapidary.
-  # 
-  # 
-  # == Feedback
-  # 
+  #
+  #
+  # ## Feedback
+  #
   # I like (and do my best to practice) XP, so I value early releases,
   # user feedback, and clean, simple, expressive code. There is always
   # room for improvement in everything I do, and Test::Unit is no
@@ -41,79 +41,84 @@ module Test # :nodoc:
   # hear about any successes you have with Test::Unit, and any
   # documentation you might add will be greatly appreciated. My contact
   # info is below.
-  # 
-  # 
-  # == Contact Information
-  # 
-  # A lot of discussion happens about Ruby in general on the ruby-talk
-  # mailing list (http://www.ruby-lang.org/en/ml.html), and you can ask
-  # any questions you might have there. I monitor the list, as do many
-  # other helpful Rubyists, and you're sure to get a quick answer. Of
-  # course, you're also welcome to email me (Nathaniel Talbott) directly
-  # at mailto:testunit@talbott.ws, and I'll do my best to help you out.
-  # 
-  # 
-  # == Credits
-  # 
+  #
+  #
+  # ## Contact Information
+  #
+  #   * [GitHub issues on
+  #     test-unit/test-unit](https://github.com/test-unit/test-unit/issues):
+  #     If you have any issues, please report them to here.
+  #
+  #   * [GitHub pull requests on
+  #     test-unit/test-unit](https://github.com/test-unit/test-unit/pulls):
+  #     If you have any patches, please report them to here.
+  #
+  #   * [ruby-talk mailing
+  #     list](https://www.ruby-lang.org/en/community/mailing-lists/):
+  #     If you have any questions, you can ask them here.
+  #
+  #
+  # ## Credits
+  #
   # I'd like to thank...
-  # 
+  #
   # Matz, for a great language!
-  # 
+  #
   # Masaki Suketa, for his work on RubyUnit, which filled a vital need in
   # the Ruby world for a very long time. I'm also grateful for his help in
   # polishing Test::Unit and getting the RubyUnit compatibility layer
   # right. His graciousness in allowing Test::Unit to supercede RubyUnit
   # continues to be a challenge to me to be more willing to defer my own
   # rights.
-  # 
+  #
   # Ken McKinlay, for his interest and work on unit testing, and for his
   # willingness to dialog about it. He was also a great help in pointing
   # out some of the holes in the RubyUnit compatibility layer.
-  # 
+  #
   # Dave Thomas, for the original idea that led to the extremely simple
   # "require 'test/unit'", plus his code to improve it even more by
   # allowing the selection of tests from the command-line. Also, without
   # RDoc, the documentation for Test::Unit would stink a lot more than it
   # does now.
-  # 
+  #
   # Everyone who's helped out with bug reports, feature ideas,
   # encouragement to continue, etc. It's a real privilege to be a part of
   # the Ruby community.
-  # 
+  #
   # The guys at RoleModel Software, for putting up with me repeating, "But
   # this would be so much easier in Ruby!" whenever we're coding in Java.
-  # 
+  #
   # My Creator, for giving me life, and giving it more abundantly.
-  # 
-  # 
-  # == License
-  # 
+  #
+  #
+  # ## License
+  #
   # Test::Unit is copyright (c) 2000-2003 Nathaniel Talbott. It is free
   # software, and is distributed under the Ruby license. See the COPYING
   # file.
-  # 
+  #
   # Exception: lib/test/unit/diff.rb is copyright (c)
   # 2008-2010 Kouhei Sutou and 2001-2008 Python Software
   # Foundation. It is free software, and is distributed
   # under the Ruby license and/or the PSF license. See the
   # COPYING file and PSFL file.
-  # 
-  # == Warranty
-  # 
+  #
+  # ## Warranty
+  #
   # This software is provided "as is" and without any express or
   # implied warranties, including, without limitation, the implied
   # warranties of merchantibility and fitness for a particular
   # purpose.
-  # 
-  # 
-  # == Author
-  # 
+  #
+  #
+  # ## Author
+  #
   # Nathaniel Talbott.
   # Copyright (c) 2000-2003, Nathaniel Talbott
   #
   # ----
   #
-  # = Usage
+  # # Usage
   #
   # The general idea behind unit testing is that you write a _test_
   # _method_ that makes certain _assertions_ about your code, working
@@ -125,7 +130,7 @@ module Test # :nodoc:
   # pieces.
   #
   #
-  # == Assertions
+  # ## Assertions
   #
   # These are the heart of the framework. Think of an assertion as a
   # statement of expected outcome, i.e. "I assert that x should be equal
@@ -137,7 +142,7 @@ module Test # :nodoc:
   # of the current assertions, see Test::Unit::Assertions.
   #
   #
-  # == Test Method & Test Fixture
+  # ## Test Method & Test Fixture
   #
   # Obviously, these assertions have to be called within a context that
   # knows about them and can do something meaningful with their
@@ -197,7 +202,7 @@ module Test # :nodoc:
   #     end
   #
   #
-  # == Test Runners
+  # ## Test Runners
   #
   # So, now you have this great test class, but you still
   # need a way to run it and view any failures that occur
@@ -208,10 +213,10 @@ module Test # :nodoc:
   # runner simply set default test runner ID to
   # Test::Unit::AutoRunner:
   #
-  #    require 'test/unit'
-  #    Test::Unit::AutoRunner.default_runner = "gtk2"
+  #     require 'test/unit'
+  #     Test::Unit::AutoRunner.default_runner = "gtk2"
   #
-  # == Test Suite
+  # ## Test Suite
   #
   # As more and more unit tests accumulate for a given project, it
   # becomes a real drag running them one at a time, and it also
@@ -228,17 +233,17 @@ module Test # :nodoc:
   # 'test/unit'. What does this mean? It means you could
   # write the above test case like this instead:
   #
-  #  require 'test/unit'
-  #  require 'test_myfirsttests'
-  #  require 'test_moretestsbyme'
-  #  require 'test_anothersetoftests'
+  #     require 'test/unit'
+  #     require 'test_myfirsttests'
+  #     require 'test_moretestsbyme'
+  #     require 'test_anothersetoftests'
   #
   # Test::Unit is smart enough to find all the test cases existing in
   # the ObjectSpace and wrap them up into a suite for you. It then runs
   # the dynamic suite using the console TestRunner.
   #
   #
-  # == Configuration file
+  # ## Configuration file
   #
   # Test::Unit reads 'test-unit.yml' in the current working
   # directory as Test::Unit's configuration file. It can
@@ -254,53 +259,58 @@ module Test # :nodoc:
   #
   # Here are sample color scheme definitions:
   #
-  #   color_schemes:
-  #     inverted:
-  #       success:
-  #         name: red
-  #         bold: true
-  #       failure:
-  #         name: green
-  #         bold: true
-  #     other_scheme:
-  #       ...
+  #     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
-  #      ...
-  #    ...
-  #
-  # SCHEME_NAME:: the name of the color scheme
-  # EVENT_NAME:: one of [success, failure, pending,
-  #              omission, notification, error]
-  # COLOR_NAME:: one of [black, red, green, yellow, blue,
-  #              magenta, cyan, white]
-  # BOOLEAN:: true or false
+  #     color_schemes:
+  #       SCHEME_NAME:
+  #         EVENT_NAME:
+  #           name: COLOR_NAME
+  #           intensity: BOOLEAN
+  #           bold: BOOLEAN
+  #           italic: BOOLEAN
+  #           underline: BOOLEAN
+  #         ...
+  #       ...
+  #
+  # SCHEME_NAME
+  # : the name of the color scheme
+  #
+  # EVENT_NAME
+  # : one of [success, failure, pending, omission, notification, error]
+  #
+  # COLOR_NAME
+  # : one of [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
+  #     runner: console
+  #     console_options:
+  #       color_scheme: inverted
+  #     color_schemes:
+  #       inverted:
+  #         success:
+  #           name: red
+  #           bold: true
+  #         failure:
+  #           name: green
+  #           bold: true
   #
-  # == Questions?
+  # ## Questions?
   #
   # I'd really like to get feedback from all levels of Ruby
   # practitioners about typos, grammatical errors, unclear statements,
@@ -331,51 +341,53 @@ module Test # :nodoc:
       # To register multiple hooks, call this method multiple times.
       #
       # Here is an example test case:
-      #   Test::Unit.at_start do
-      #     # ...
-      #   end
-      #
-      #   class TestMyClass1 < Test::Unit::TestCase
-      #     class << self
-      #       def startup
-      #         # ...
-      #       end
-      #     end
       #
-      #     def setup
+      #     Test::Unit.at_start do
       #       # ...
       #     end
       #
-      #     def test_my_class1
-      #       # ...
-      #     end
+      #     class TestMyClass1 < Test::Unit::TestCase
+      #       class << self
+      #         def startup
+      #           # ...
+      #         end
+      #       end
       #
-      #     def test_my_class2
-      #       # ...
-      #     end
-      #   end
+      #       def setup
+      #         # ...
+      #       end
       #
-      #   class TestMyClass2 < Test::Unit::TestCase
-      #     class << self
-      #       def startup
+      #       def test_my_class1
       #         # ...
       #       end
-      #     end
       #
-      #     def setup
-      #       # ...
+      #       def test_my_class2
+      #         # ...
+      #       end
       #     end
       #
-      #     def test_my_class1
-      #       # ...
-      #     end
+      #     class TestMyClass2 < Test::Unit::TestCase
+      #       class << self
+      #         def startup
+      #           # ...
+      #         end
+      #       end
       #
-      #     def test_my_class2
-      #       # ...
+      #       def setup
+      #         # ...
+      #       end
+      #
+      #       def test_my_class1
+      #         # ...
+      #       end
+      #
+      #       def test_my_class2
+      #         # ...
+      #       end
       #     end
-      #   end
       #
       # Here is a call order:
+      #
       # * at_start
       # * TestMyClass1.startup
       # * TestMyClass1#setup
@@ -415,51 +427,53 @@ module Test # :nodoc:
       # To register multiple hooks, call this method multiple times.
       #
       # Here is an example test case:
-      #   Test::Unit.at_exit do
-      #     # ...
-      #   end
-      #
-      #   class TestMyClass1 < Test::Unit::TestCase
-      #     class << self
-      #       def shutdown
-      #         # ...
-      #       end
-      #     end
       #
-      #     def teardown
+      #     Test::Unit.at_exit do
       #       # ...
       #     end
       #
-      #     def test_my_class1
-      #       # ...
-      #     end
+      #     class TestMyClass1 < Test::Unit::TestCase
+      #       class << self
+      #         def shutdown
+      #           # ...
+      #         end
+      #       end
       #
-      #     def test_my_class2
-      #       # ...
-      #     end
-      #   end
+      #       def teardown
+      #         # ...
+      #       end
       #
-      #   class TestMyClass2 < Test::Unit::TestCase
-      #     class << self
-      #       def shutdown
+      #       def test_my_class1
       #         # ...
       #       end
-      #     end
       #
-      #     def teardown
-      #       # ...
+      #       def test_my_class2
+      #         # ...
+      #       end
       #     end
       #
-      #     def test_my_class1
-      #       # ...
-      #     end
+      #     class TestMyClass2 < Test::Unit::TestCase
+      #       class << self
+      #         def shutdown
+      #           # ...
+      #         end
+      #       end
       #
-      #     def test_my_class2
-      #       # ...
+      #       def teardown
+      #         # ...
+      #       end
+      #
+      #       def test_my_class1
+      #         # ...
+      #       end
+      #
+      #       def test_my_class2
+      #         # ...
+      #       end
       #     end
-      #   end
       #
       # Here is a call order:
+      #
       # * TestMyClass1#test_my_class1
       # * TestMyClass1#teardown
       # * TestMyClass1#test_my_class2