ruby.git/test/optparse/test_optparse.rb, branch v4.0.3

[ruby/optparse] JRuby does not have EXECUTABLE_EXTS in RbConfg::CONFIG

2025-06-29T07:52:46+00:00

https://github.com/ruby/optparse/commit/15b2f00b6b

[ruby/optparse] Fix OptionParser#program_name not to strip suffix unexpectedly

2025-06-29T07:52:45+00:00

https://github.com/ruby/optparse/commit/740ffa76c0

[ruby/optparse] Make the result of `tty?` obtainable with flexible stdout

2025-03-10T10:19:58+00:00

In mock testing for stdout, `StringIO.new` is sometimes used to redirect the output.
In such cases, the assignment is done with `$stdout = StringIO.new`, not the constant `STDOUT`.
e.g., https://github.com/rubocop/rubocop/blob/v1.71.1/lib/rubocop/rspec/shared_contexts.rb#L154-L164

After assigning `StringIO.new`, `$stdout.tty?` returns `false`,
allowing the standard output destination to be switched during test execution.

```ruby
STDOUT.tty?       # => true
StringIO.new.tty? # => false
```

However, since `STDOUT.tty?` returns `true`, a failure occurred in environments
where the environment variables `RUBY_PAGER` or `PAGER` are set.
e.g., https://github.com/rubocop/rubocop/pull/13784

To address this, `STDOUT` has been updated to `$stdout` so that the result of `tty?` can be flexibly overridden.

A potential concern is that `$stdout`, unlike `STDOUT`,
does not always represent the standard output at the time the Ruby process started.
However, no concrete examples of issues related to this have been identified.

`STDOUT.tty?` is the logic of optparse introduced in https://github.com/ruby/optparse/pull/70.

This PR replaces `STDOUT` with `$stdout` throughout, based on the assumption
that `$stdout` is sufficient for use with optparse.

https://github.com/ruby/optparse/commit/262cf6f9ac

[ruby/optparse] Fix parsing array arguments with `:into` option

2024-08-05T02:28:12+00:00

https://github.com/ruby/optparse/commit/19700e96d8

[ruby/optparse] Invoke pager for `--help`

2024-03-01T07:10:08+00:00

https://github.com/ruby/optparse/commit/77dccce37c

[ruby/optparse] Add `exact:` keyword argument

2024-02-23T12:16:59+00:00

https://github.com/ruby/optparse/commit/07e83673a8

[ruby/optparse] Respect default values in block parameters

2024-02-09T10:58:19+00:00

Fix https://github.com/ruby/optparse/pull/55

https://github.com/ruby/optparse/commit/9d53e74aa4

[ruby/optparse] Fix `require_exact` to work with options defined as `--[no]-something`

2024-02-09T03:31:13+00:00

https://github.com/ruby/optparse/commit/4e346ad337

[ruby/optparse] The encoding argument of `Regexp.new` has been ignored since 1.9

2022-12-21T05:09:12+00:00

https://github.com/ruby/optparse/commit/766f567405

[ruby/optparse] Fix the test failure i ruby/ruby

2022-11-28T16:20:40+00:00

```
$ make test-all TESTS=test/optparse/
...

[148/178] TestOptionParserDidYouMean#test_raise_unknown = 0.00 s
  1) Failure:
TestOptionParserDidYouMean#test_raise_unknown [/home/mame/work/ruby/test/optparse/test_optparse.rb:106]:
<["--bar"]> expected but was
<[]>.
```

In the old test/unit (bundled in ruby/ruby), when a test class inherits from
another test class, the child class runs all the tests defined in the parent
class.
However, it looks like the new test/unit does not do so. This is because the
test failure does not occur in ruby/optparse.

As a tentative solution, this changes the option names in TestOptionParser to
avoid the name conflict with TestOptionParserDidYouMean.

https://github.com/ruby/optparse/commit/fee86ef7a4