> From: Joseph Pelrine <
[hidden email]>
> Date: 27 mars 2006 09:15:11 HAEC
> To: stéphane ducasse <
[hidden email]>
> Subject: Re: SUnit: Skipping tests?
>
> The simple way is to set up "environment variables" for tests, and
> have a TestCase subclass check that these vars are valid as a
> preconditoin to running the tests. The perfect way is to re-do
> SUnit, adding yet another state to {pass|fail|error}, and another
> exception to mark this. Note the additional level of complexity
> this brings to TestResult>>#runCase:
>
> I did the first, and wrote to the Transcript a log of which tests
> were skipped. I think that's the was Alan did it too.
>
> Joseph
> At 08:20 27.03.2006, stéphane ducasse wrote:
>> And whaat was your solution?
>>
>> Stef
>> On 27 mars 06, at 07:39, Joseph Pelrine wrote:
>>
>>> Sure, I've done that already. IIRC, Glorp has these kind of tests.
>>>
>>> Joseph
>>> At 07:30 27.03.2006, stéphane ducasse wrote:
>>>> what do you think on that?
>>>> I thought I would add a test kind.
>>>>
>>>> Stef
>>>>
>>>> Begin forwarded message:
>>>>
>>>>> From: Andreas Raab <
[hidden email]>
>>>>> Date: 27 mars 2006 01:08:17 HAEC
>>>>> To: The general-purpose Squeak developers list <squeak-
>>>>>
[hidden email]>
>>>>> Subject: SUnit: Skipping tests?
>>>>> Reply-To: The general-purpose Squeak developers list <squeak-
>>>>>
[hidden email]>
>>>>>
>>>>> Hi Folks -
>>>>>
>>>>> I am in the interesting situation that I'm writing a few tests
>>>>> that
>>>>> require large data sets for input and where I don't want people to
>>>>> require to download the data sets. My problem is while it's
>>>>> easy to
>>>>> determine that the data is missing and skip the test there isn't a
>>>>> good way of relaying this to the user. From the user's point of
>>>>> view "all tests are green" even though that statement is
>>>>> completely
>>>>> meaningless and I'd rather communicate that in a way that says "X
>>>>> tests skipped" so that one can look at and decide whether it's
>>>>> useful to re-run the tests with the data sets or not.
>>>>>
>>>>> Another place where I've seen this to happen is when platform
>>>>> specific tests are involved. A test which cannot be run on some
>>>>> platform should be skipped meaningfully (e.g., by telling the user
>>>>> it was skipped) rather than to appear green and working.
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> Cheers,
>>>>> - Andreas
>>>
>>> --
>>> Joseph Pelrine [ | ]
>>> MetaProg GmbH
>>> Email:
[hidden email]
>>> Web:
http://www.metaprog.com>>>
>>> You don't become enormously successful without encountering some
>>> really interesting problems.
>>> - Mark Victor Hansen
>>>
>>
>
> --
> Joseph Pelrine [ | ]
> MetaProg GmbH
> Email:
[hidden email]
> Web:
http://www.metaprog.com>
> You don't become enormously successful without encountering some
> really interesting problems.
> - Mark Victor Hansen
>
>
Locked
