[Etoys] Unit Test
bert at freudenbergs.de
Wed Sep 26 20:54:50 EDT 2007
I see. Well. The simplest then would be to always declare the
TestCase subclass in your changeset, even if you are just adding
- Bert -
On Sep 27, 2007, at 2:05 , Takashi Yamamiya wrote:
> The problem is to change a test method at a test class which is
> in the image. For example, if I want to change LanguageEditorTest
> includes tests for gettext exporter. But I can't do because
> removes all test cases while the build process.
> Adding new test class causes no problem even now. Although the
> strangely becomes ProtoObject.
> So keeping only TestCase class doesn't help.
> - Takashi
> Bert Freudenberg wrote:
>> On Sep 27, 2007, at 0:57 , Takashi Yamamiya wrote:
>>> 2: Include TestCases into etoys.image: I measured the impact of
>>> including test cases today. The difference is 384K. 17,871K with
>>> tests, 17,487K without tests in both #1664 with Launcher
>>> project. Even we can strip some unused test classes.
>> I think the update stream is convenient for people like Kim who
>> do not want to wait for the next release, or those for which
>> always downloading a whole new image is inconvenient.
>> Wouldn't it work if we include just the TestCase class in the
>> deployed image so file-ins succeed?
More information about the etoys-dev