%#--
%# Copyright 2009 Suraj N. Kurapati
%# See the LICENSE file for details.
%#++
%|chapter "History"
% sean_ohalpin_musing = "[Sean O'Halpin's musing](http://www.ruby-forum.com/topic/183354#801895)"
%|history
For the longest time, I took <%= competitors.link_for 'Test::Unit' %> and <%= competitors.link_for 'RSpec' %> for granted. They were the epitomy of modern Ruby practice; the insurmountable status quo; immortalized in books, conferences, and blogs alike.
Why would *anyone* think of using anything remotely different, let alone be foolish enough to write an alternative testing library when these are clearly *good enough*?
Recent experiments in assertion testing libraries smashed my world view:
* <%= competitors.link_for 'assert{ 2.0 }' %>
* <%= competitors.link_for 'Testy' %>
* <%= competitors.link_for 'Verify' %>
The status quo was certainly *not* "good enough", as I had so blindly believed all these years. In fact, they were *verbose* behemoths that chose to encode endless permutations of conjecture into methods.
Empowered by this revelation and inspired by <%= sean_ohalpin_musing %> on alternative names for assertion methods, I rose to challenge the status quo.
%|section "Version 1.0.0 (2009-05-03)"
This release improves default choices, adds emulation layers to mimic other testing libraries, and fixes some bugs.
%|paragraph "Incompatible changes"
* The `:debug` option is now enabled by default and is no longer linked to the value of `$DEBUG`.
* `Dfect.run()` now appends to previous results by default.
This behavior can be disabled by passing `false` to the method.
%|paragraph "New features"
* Add emulation layers to mimic other testing libraries:
* dfect/unit --- Test::Unit
* dfect/mini --- Minitest
* dfect/spec --- RSpec
%|paragraph "Bug fixes"
* Do not blindly replace `Class#to_yaml`; it might be fixed someday.
%|paragraph "Housekeeping"
* Add <%= xref "Motivation" %> section in user manual to promote interactive debugging.
* Add brief <%= xref "History" %> of this project's inception.
* Remove redundant assertions for F!() and T!() methods in test suite.
* Add copyright notice at the top of every file.
%|section "Version 0.1.0 (2009-04-28)"
This release adds new variations to assertion methods, fixes several bugs, and improves test coverage.
%|paragraph "Thank you"
* François Beausoleil contributed patches for both code *and* tests! :-)
%|paragraph "New features"
* Added <%= xref "Negation", "negation (m!)" %> and <%= xref "Sampling", "sampling (m?)" %> variations to <%= xref "Assertions", "assertion methods" %>.
These new methods implement assertion functionality missing so far (previously we could not assert that a given exception was NOT thrown) and thereby allow us to fully test Dfect using itself.
* Added documentation on <%= xref "Insulation", "how to insulate tests" %> from the global Ruby namespace.
%|paragraph "Bug fixes"
* The `E()` method did not consider the case where a block does not raise anything as a failure. ---*François Beausoleil*
* When creating a report about an assertion failure, an exception would be thrown if any local variables pointed to an empty array.
* The `Dfect::<()` method broke the inheritance-checking behavior of the < class method.
Added a bypass to the originial behavior so that `RCov::XX` can properly generate a report about code that uses Dfect.
* Added workaround for YAML error when serializing a class object:
TypeError: can't dump anonymous class Class
%|paragraph "Housekeeping"
* Filled the big holes in test coverage. Everything except the runtime debugging logic is now covered by the unit tests.
%|section "Version 0.0.0 (2009-04-13)"
This is the first public release of <%= $project %>. It was inspired by <%= sean_ohalpin_musing %> on alternative names for assertion methods.