Thu, 12 Feb 2015 00:26:57 +0000 Oops, implemented missing #dictionaryClass method. working_v5_0
Jan Vrany <jan.vrany@fit.cvut.cz> [Thu, 12 Feb 2015 00:26:57 +0000] rev 617
Oops, implemented missing #dictionaryClass method.
Tue, 27 Jan 2015 09:51:19 +0000 Reverted TestCase>>debug to work with MiniTestRunner working_v5_0
Jan Vrany <jan.vrany@fit.cvut.cz> [Tue, 27 Jan 2015 09:51:19 +0000] rev 616
Reverted TestCase>>debug to work with MiniTestRunner
Thu, 17 Jul 2014 15:28:02 +0100 Fixed condition in TestCaseOutcome class>>rememberedOutcomeFor: working_v5_0
Jan Vrany <jan.vrany@fit.cvut.cz> [Thu, 17 Jul 2014 15:28:02 +0100] rev 615
Fixed condition in TestCaseOutcome class>>rememberedOutcomeFor:
Mon, 14 Jul 2014 21:58:21 +0100 Refactored remembering of TestCaseOutcomes. working_v5_0
Jan Vrany <jan.vrany@fit.cvut.cz> [Mon, 14 Jul 2014 21:58:21 +0100] rev 614
Refactored remembering of TestCaseOutcomes. TestCaseOutcomes are no longer remembered in class instance var of the TestCase but rather in one global dictionary on TestCaseOutcome class. The top-level weak dictionary uses test method as a key and second-level dictionary as value. This ensures that when a test method is changed, sooner or later (now obsolete) remebered outcomes are reclamed by the GC. The second-level dictionary uses test case class as a key and outcome as value. This is used to keep outcomes for inherited test cases. This dictionary is also weak, ensuring that when the class is unloaded or changed, outcomes are reclamed. To reduce a number of weak objects a special TestCaseOutcomeWeakIdentityDictionary is used. It optimizes the most common case when there are no inherited testcases.
Wed, 09 Jul 2014 23:00:04 +0100 Reverted TestCase>>debug to original SUnit implementation and made TestFailure proceedable. working_v5_0
Jan Vrany <jan.vrany@fit.cvut.cz> [Wed, 09 Jul 2014 23:00:04 +0100] rev 613
Reverted TestCase>>debug to original SUnit implementation and made TestFailure proceedable. The code in TestCase>>debug was too elaborate. The purpose was to be able to proceed to see what next assertion is failing. This could be easily achieved by making TestFailure a resumable exception (by means of #mayProceed)
Wed, 09 Jul 2014 22:13:52 +0100 Fix tests that assert's TestResult printString. working_v5_0
Jan Vrany <jan.vrany@fit.cvut.cz> [Wed, 09 Jul 2014 22:13:52 +0100] rev 612
Fix tests that assert's TestResult printString. Now the TestResult>>printString contains also a number of tests skipped. Assert values in tests have been updated acordingly.
Wed, 09 Jul 2014 21:35:30 +0100 Project definition fixed and HG configured as for CVS mirror repository. working_v5_0
Jan Vrany <jan.vrany@fit.cvut.cz> [Wed, 09 Jul 2014 21:35:30 +0100] rev 611
Project definition fixed and HG configured as for CVS mirror repository.
Fri, 08 May 2015 12:28:56 +0200 class: TestCaseOutcome
Claus Gittinger <cg@exept.de> [Fri, 08 May 2015 12:28:56 +0200] rev 610
class: TestCaseOutcome changed: #=
Thu, 23 Apr 2015 03:47:43 +0000 update tags
convert-repo [Thu, 23 Apr 2015 03:47:43 +0000] rev 609
update tags
Wed, 22 Apr 2015 20:04:02 +0200 class: TestResultStX
Stefan Vogel <sv@exept.de> [Wed, 22 Apr 2015 20:04:02 +0200] rev 608
class: TestResultStX changed: #performCase: Use CharacterWriteStream for Unicode compatibility
(0) -300 -100 -10 +10 +100 tip