Upload it at our Wiki Upload Page, and then add a note here!
October 30, 2000, uploaded SUnit 2.7 for VAST 5.0 with the following extensions:
- added #testMe class method to the TestCaseAbstract class to allow test suites to be included (visible) or excluded in the TeamTestRunner UI.
- added support for creating and running test scripts under the TestCaseAbstract class hierarchy. This allow groups of selected test suites to run in the UI instead of just 'one' suite or 'all' suites.
- added support for running inherited test cases.
- subclassed TestRunner with TeamTestRunner to allow 'visible' test suites or test scripts to run.
The zipped Envy .DAT file is downloadable here.
Enjoy, Long On
Today, July 12, 2000, we have uploaded a zip file containing some obvious extensions. They are mostly syntactic sugar over the assert: method. Some of these methods have been inspired by JUnit. TestSuite>>debug runs every case of the suite in debug mode TestCase>>assert:equals: succeeds if arguments are equal TestCase>>assert:same: succeeds if arguments are identical TestCase>>assertNotNil: succeeds if argument is not nil TestCase>>assertNil: succeeds if argument is nil TestCase>>assertEmpty: succeeds if collection argument is empty TestCase>>assertSize:of: succeeds if collection argument has specified size TestCase>>assertZero: succeeds if number argument is equal to 0
We also added some convenience methods for grouping tests in a (VisualWorks?) Category or an Envy Application. However, these extensions are environment specific:
TestSuite class>>suiteFromCategory: creates a TestSuite from all the subclasses of TestCase in the specified category TestSuite class>>suiteFromApplication: creates a TestSuite from all the subclasses of TestCase in an Envy-Application
We have added tests for all methods to SUnitTest.
You can find the .pcl/.pst/.dat files in a zip-file for VisualWorks3.0 with Envy 4 here.
Sander Tichelaar and Matthias Rieger
Today, May 30, 2000, I changed two things: I fixed test cases that used non namespace class names in Strings and renamed the zip file to SUnitInNamespacesFor5i.zip. Again: VisualWorks 5i.1 and Envy 6.2 for VisualWorks 5i.
Georg Heeg
Today, May 16, 2000, I took the VW5i-part of Benny's work and pushed it into the Namespace XProgramming.SUnit. I rewrote the parcels and imported them into Envy 6.2.
In here you'll find *.pcl, *.pst and SUnit.dat files.
enjoy, Georg Heeg
I don't know what got into me, but I decided to do some therapeutic packaging to Sames wonderful work.
so, god forbids, what have I done? I 'mangled' only the VW and VA versions.
- all versions now add a 'Test Runner' entry to the launcher's Tools menu.
- the VW versions add a 'Test Runner' icon to the launcher's tool bar.
- I named all parcels in their short form: SUnit, SUnitUI, SUnitTests.
- I incorporated the SUnitPreload parcels into SUnit. the reasoning is that since parcels allow for a method to exists in a few parcels, then it wouldn't matter when a later ANSI compatibility parcel load.
- I created one Envy config map that includes the VA version (v >= 4.5), and the VW version (v >= 3.0).
- I patched the VW5i version so it will handle TestCases in nested namespaces. Of all the vesrions, this is the only base change.
the download is available here. enjoy, Benny Sadeh
I have an extended SUnit Browser, currently for IBM Smalltalk and Dolphin Smalltalk 4.0. Both versions currently available here.
Jeff Odell