Tags: rubyworks/rubytest

Maintenance release v0.9.0 — modernize and merge CLI

Merge rubytest-cli back into rubytest with bin/rubytest executable.
Replace custom Indexer system with standard gemspec, Travis CI with
GitHub Actions, and Assembly with Rakefile. Remove Ruby 1.9 compat code,
simplify version handling. Fix typos, update URLs to HTTPS, move site
from gh-pages to docs/, and clean up obsolete files.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Version 0.7 is a significant release. The library has been simplified

by spinning-off both the command-line tool and the Rake task as
`rubytest-cli` and `rubytest-rake` respectively. This was done for a
couple of good reasons: a) It focuses the the library on it's core
functionality and b) and it makes the library suitable for becoming
a Ruby standard library, should that ever become a possibility.

This release of Ruby Test takes a hard step back and reconsiders how

to handle configuration from the ground up. Current users of Ruby Test
will probably have to make some adjustments. Our apologies for the extra
work. But the whole thing simply got more complicated than it needed to
be and it was decided that conventional simplicity, with the option
unconventional complexity, was the best approach.

To make a long story short... There is no default config file anymore.
The `-p/--profile` command line option has been removed; replaced by
a `-c/--config` option which requires a file relative to the working
directory. In addition the configuration API had been changed from `Test.run`
or `Test.configure`, to adopt the common convention, and it no longer takes
a profile name for an argument. `Test.run` still has the same interface as
`Test.configure` but it will now run tests immediately! So be sure to change
that if you used it the past. Lastly, Ruby Test now supports DotOpts out of
the box, so its easier then ever to setup default command line options.

This release simply updates configuraiton code to work with RC v0.4.0.

Adjust Config to look for a project's `.index` file for load path, in…

…stead of

a `.ruby` file. Also, this will only happen now if configured to do so,
i.e. via the `-a/--autopath` option on the command line.

Courtier was renamed to RC. And the previous release overlooked the r…

…equirement

on RC altogether. This release corrects the issue making it optional.

This release improves the command line interface, the handling of con…

…figuration and provides a mechinism for adding custom test observers. The later can be used for things like mock library verifcation steps.

This release primarily consists of implementation tweaks. The most si…

…gnificant

change is in support of exception priorities, which justify the major verison bump.

With this release Ruby Test is essentially feature complete. Of cours…

…e there

are plenty of tweaks and improvements yet to come, but Ruby Test is fully usable
at this point. Only one major aspect of the design remains in question --the
way per-testcase "before and after all" advice is handled. Other than that
the API fairly solid, even as this early state of development. Always helps
when you have a spec to go by!

First release of Ruby Test.