|
|
Darren New wrote:
> Stephen wrote:
>> Are we having a “two countries separated by a common language” moment
>> here or is it me speaking fluent “Stephen”? :-)
>
> I don't know, but I'm talking about the contents of a specific unit
> test, given that other unit test have already passed or failed.
>
> I know what I want to test. I'm saying that if it takes 15 steps to get
> to the 16'th step I want to test, and I already tested the 15 steps in
> another test, do I need to re-test them in the 16'th step?
>
> If I want to test "media player elapsed-time counter stops incrementing
> and stays at 20 seconds if I pause the media player after 20 seconds of
> playing", do I also need to test "media player constructor works, media
> player starts playing, elapsed time counter increases one second per
> second" in the "pause" unit test?
>
> Or, in your example, if your first unit test tests that what the
> developer gave you in the upload is right, do you have to test that
> again in the second test that submits it to the SAP upload interface?
>
>
The answer is no, you don’t need to retest previously passed tests, that
is the whole idea of *unit* tests.
Sorry if I over complicated things.
--
Best Regards,
Stephen
Post a reply to this message
|
|