I need to set up various special state on all tests of a specialized
Suite during initialization of the Suite.  But after creating the
tests, SUnit then promptly throws them all away which is not only
wasteful it loses all of my needed additional-state).

setUp and tearDown are intended to, well, set up and tear down any
test.  Any test that cannot "run again" is broken because it means its
setUp and tearDown methods don't do the job they're supposed to.

If no objections, I will push this to trunk and delete the
#testRanOnlyOnce test.

Thanks,
  Chris

On Fri, Jan 4, 2013 at 3:33 PM,  <commits at source.squeak.org> wrote:
> A new version of SUnit was added to project The Inbox:
> http://source.squeak.org/inbox/SUnit-cmm.90.mcz
>
> ==================== Summary ====================
>
> Name: SUnit-cmm.90
> Author: cmm
> Time: 4 January 2013, 3:33:36.616 pm
> UUID: 8533f0b4-2587-412b-b465-4ad7f20331d0
> Ancestors: SUnit-ul.89
>
> - Do not wipe out pre-initialized state on TestCases.  Tests do not need to be prevented from running more than once if proper setUp/tearDown methods are present.
>
> =============== Diff against SUnit-ul.89 ===============
>
> Item was changed:
>   ----- Method: TestCase>>debug (in category 'running') -----
>   debug
> +       self resources do:
> +               [ : res | res isAvailable ifFalse: [ ^ res signalInitializationError ] ].
> +       [ self runCase ] ensure:
> +               [ self resources do:
> +                       [ : each | each reset ] ]!
> -       self resources do: [:res |
> -               res isAvailable ifFalse: [^res signalInitializationError]].
> -       [(self class selector: testSelector) runCase]
> -               ensure: [self resources do: [:each | each reset]]
> -                       !
>
>