Be the first to post a text review of shunit2. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• Tracker comment added

  Anonymous commented on the failX functions not working? artifact

  posted by nobody 505 days ago

• Tracker artifact added

  Anonymous created the failX functions not working? artifact

  posted by nobody 505 days ago

• shUnit2 has moved!

  shUnit2 is now being hosted at http://code.google.com/p/shunit2/.

  posted by sfsetse 542 days ago

• Code committed

  sfsetse committed revision 167 to the shunit2 SVN repository, changing 2 files

  posted by sfsetse 574 days ago

• Code committed

  sfsetse committed revision 166 to the shunit2 SVN repository, changing 2 files

  posted by sfsetse 588 days ago

• Code committed

  sfsetse committed revision 165 to the shunit2 SVN repository, changing 1 files

  posted by sfsetse 605 days ago

• Code committed

  sfsetse committed revision 164 to the shunit2 SVN repository, changing 1 files

  posted by sfsetse 606 days ago

• Code committed

  sfsetse committed revision 163 to the shunit2 SVN repository, changing 1 files

  posted by sfsetse 606 days ago

• shUnit2 2.1.X (development) 2.1.3 file released: shunit2-2.1.3.tgz

  Changes in shUnit2 2.1.X ======================== Changes with 2.1.3 ------------------ Added some explicit variable defaults, even though the variables are set, as they sometimes behave strange when the script is canceled. Additional workarounds for zsh compatibility. shUnit2 now exits with a non-zero exit code if any of the tests failed. This was done for automated testing frameworks. Tests that were skipped are not considered failures, and do not affect the exit code. Changed detection of STDERR output in unit tests. Changes with 2.1.2 ------------------ Unset additional variables that were missed. Added checks and workarounds to improve zsh compatibility. Added some argument count checks ``assertEquals()``, ``assertNull()``, and ``assertSame()`` Changes with 2.1.1 ------------------ Fixed bug where ``fail()`` was not honoring skipping. Fixed problem with ``docs-docbook-prep`` target that prevented it from working. (Thanks to Bryan Larsen for pointing this out.) Changed the test in ``assertFalse()`` so that any non-zero value registers as false. (Credits to Bryan Larsen) Major fiddling to bring more in line with `JUnit <http://junit.org/>`. Asserts give better output when no message is given, and failures now just fail. It was pointed out that the simple 'failed' message for a failed assert was not only insufficient, it was nonstandard (when compared to JUnit) and didn't provide the user with an expected vs actual result. The code was revised somewhat to bring closer into alignment with JUnit (v4.3.1 specifically) so that it feels more "normal". (Credits to Richard Jensen) As part of the JUnit realignment, it was noticed that fail*() functions in JUnit don't actually do any comparisons themselves. They only generate a failure message. Updated the code to match. Added self-testing unit tests. Kinda horkey, but they did find bugs during the JUnit realignment. Fixed the code for returning from asserts as the return was being called before the unsetting of variables occurred. (Credits to Mathias Goldau) The assert(True|False)() functions now accept an integer value for a conditional test. A value of '0' is considered 'true', while any non-zero value is considered 'false'. All public functions now fill use default values to work properly with the '-x' shell debugging flag. Fixed the method of percent calculation for the report to get achieve better accuracy. Changes with 2.1.0 (since 2.0.1) -------------------------------- This release is a branch of the 2.0.1 release. Moving to `reStructured Text <http://docutils.sourceforge.net/rst.html>`_ for the documentation. Fixed problem with ``fail()``. The failure message was not properly printed. Fixed the ``Makefile`` so that the DocBook XML and XSLT files would be downloaded before parsing can continue. Renamed the internal ``__SHUNIT_TRUE`` and ``__SHUNIT_FALSE`` variables to ``SHUNIT_TRUE`` and ``SHUNIT_FALSE`` so that unit tests can "use" them. Added support for test "skipping". If skipping is turned on with the ``startSkip()`` function, ``assert`` and ``fail`` functions will return immediately, and the skip will be recorded. The report output format was changed to include the percentage for each test result, rather than just those successful. .. $Revision: 139 $ .. vim:ft=rst:spell:textwidth=80

  posted 607 days ago

• File released: /shUnit2 2.1.X (development)/2.1.3/shunit2-2.1.3.tgz

  posted 607 days ago