Home

Welcome to Ruby Test's User Documentation. This documentation is here to elucidate the usage of Ruby Test by test framework developers test and testers alike. Fee free to participate in it's improvement.

For test framework developers the complete Specification elucidates the full API. A test framework can support the API directly, via modifications to its classes, or it can create an adapter that converts from the framework's structure to a set of objects that Ruby Test can handle.

Ruby Test is a very easy to support. For most test frameworks it takes only a small adapter file. Other test frameworks were designed to use Ruby Test from the start. Here is a list of test Frameworks currently supporting Ruby Test.

Ruby Test support the concept of Hard Testing vs. Soft Testing. Hard testing means the test procedures must return true in order to pass, otherwise an assertion error is raised. This allows tests to written without the use of an assertion framework. Soft testing, on the other hand, requires the use of an assertions framework in order to make test assertions --the return value of a test procedure is simply ignored. The default mode is soft testing. To change it, set the mode via the hard configuration option.

Test::Runner.hard = true