# Buildsheet autogenerated by ravenadm tool -- Do not edit. NAMEBASE= ruby-minitest VERSION= 5.22.3 KEYWORDS= ruby VARIANTS= v31 v32 v33 SDESC[v31]= Comple suite of testing facilities (v31) SDESC[v32]= Comple suite of testing facilities (v32) SDESC[v33]= Comple suite of testing facilities (v33) HOMEPAGE= https://github.com/minitest/minitest CONTACT= Ruby_Automaton[ruby@ironwolf.systems] DOWNLOAD_GROUPS= main SITES[main]= RUBYGEMS/ DISTFILE[1]= minitest-5.22.3.gem:main DIST_SUBDIR= ruby DF_INDEX= 1 SPKGS[v31]= single SPKGS[v32]= single SPKGS[v33]= single OPTIONS_AVAILABLE= RUBY31 RUBY32 RUBY33 OPTIONS_STANDARD= none VOPTS[v31]= RUBY31=ON RUBY32=OFF RUBY33=OFF VOPTS[v32]= RUBY31=OFF RUBY32=ON RUBY33=OFF VOPTS[v33]= RUBY31=OFF RUBY32=OFF RUBY33=ON DISTNAME= minitest-5.22.3 GENERATED= yes [RUBY31].USES_ON= gem:v31 [RUBY32].USES_ON= gem:v32 [RUBY33].USES_ON= gem:v33 [FILE:2004:descriptions/desc.single] minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking. "I had a class with Jim Weirich on testing last week and we were allowed to choose our testing frameworks. Kirk Haines and I were paired up and we cracked open the code for a few test frameworks... I MUST say that minitest is *very* readable / understandable compared to the 'other two' options we looked at. Nicely done and thank you for helping us keep our mental sanity." -- Wayne E. Seguin minitest/test is a small and incredibly fast unit testing framework. It provides a rich set of assertions to make your tests clean and readable. minitest/spec is a functionally complete spec engine. It hooks onto minitest/test and seamlessly bridges test assertions over to spec expectations. minitest/benchmark is an awesome way to assert the performance of your algorithms in a repeatable manner. Now you can assert that your newb co-worker doesn't replace your linear algorithm with an exponential one! minitest/mock by Steven Baker, is a beautifully tiny mock (and stub) object framework. minitest/pride shows pride in testing and adds coloring to your test output. I guess it is an example of how to write IO pipes too. :P minitest/test is meant to have a clean implementation for language implementors that need a minimal set of methods to bootstrap a working test suite. For example, there is no magic involved for test-case discovery. "Again, I can't praise enough the idea of a testing/specing framework that I can actually read in full in one sitting!" -- Piotr Szotkowski Comparing to rspec: rspec is a testing DSL. minitest is ruby. -- Adam Hawkins, "Bow Before MiniTest" minitest doesn't reinvent anything that ruby already provides, like: classes, modules, inheritance, methods. This means you only have to learn ruby to use minitest and all of your regular OO practices like extract-method refactorings still apply. [FILE:103:distinfo] ea84676290cb5e2b4f31f25751af6050aa90d3e43e4337141c3e3e839611981e 99328 ruby/minitest-5.22.3.gem