minitest provides a complete suite of testing facilities supporting
TDD, BDD, mocking, and benchmarking.
minitest/unit 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/unit 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 B., is a beautifully tiny mock object
framework.
minitest/pride shows pride in testing and adds coloring to your test
output.
minitest/unit 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.
Changes:
2.2.2 / 2011-06-01
2 bug fixes:
Got rid of the trailing period in message for assert_equal.
(tenderlove)
What’s the purpose of holding on to the dead rubyforge.org project site
for your good packages if it is not maintained and obviously not the
primary
landing zone for the project anymore?
Keep up the good work nevertheless, greetings,
– Matthias
We don’t upload to rubyforge.org anymore or update the news. Since
nobody reads that stuff anyhow I don’t see the problem but I can
certainly try to delete all the news posts.
I can update the README to make that more clear.
Do note that I only use github for mirroring the source.
Whats the purpose of holding on to the dead rubyforge.org project site for your
good packages if it is not maintained and obviously not the primary landing zone
for the project anymore?
Content preview: Hi, On 02.06.2011 00:58, Ryan D. wrote: > minitest
version
2.2.2 has been released! > > * http://rubyforge.org/projects/bfts
The news
sound promising, but is it the wrong link? The most recent version
there’s
is 2.0.0 and latest news says 1.4.2 released … ? Btw, can’t find
any documentation
at all there also. […]
The news sound promising, but is it the wrong link? The most recent
version there’s is 2.0.0 and latest news says 1.4.2 released … ? Btw,
can’t find any documentation at all there also.
The news sound promising, but is it the wrong link? The most recent
version there’s is 2.0.0 and latest news says 1.4.2 released … ? Btw,
can’t find any documentation at all there also.
Again, Thanks for pointing this out… I’ve since updated it (and all my
other major projects) to rdoc’s dictionary lists so I can say:
We don’t upload to rubyforge.org anymore or update the news. Since nobody reads
that stuff anyhow I don’t see the problem but I can certainly try to delete all
the news posts.
I can update the README to make that more clear.
Do note that I only use github for mirroring the source.
Thanks for the clarification, makes sense. In this case I’d suggest to
update the README to indicate github as the primary home page, cause it
has all
the current sources, SCM activities and a nice README auto display. And
the link to Rubyforge should be on 2nd place, probably introduced as
“Bug
Tracking at [http://…]”.
And, don’t forget to update your other seattlerb projects in the same
way …
Content preview: On 28.06.2011 02:36, Ryan D. wrote: > home ::
> rdoc :: http://bfts.rubyforge.org/minitest That’s really great!
Whenever
I came to rubyforge I literally felt lost there. A proper github
link these
days is a live saver. […]
