Re: [StGit PATCH] Added test case for stg refresh

From: David Kågedal <davidk@lysator.liu.se>
Date: Nov 22, 2007, 08:38 UTC
Message-ID: <87pry2u131.fsf@lysator.liu.se>
In-Reply-To: <b0943d9e0711220015r64d1a5c2y25dfa44610864c99@mail.gmail.com>

"Catalin Marinas" <catalin.marinas@gmail.com> writes:

Show 13 quoted lines

> On 22/11/2007, David Kågedal <davidk@lysator.liu.se> wrote:
>> "Catalin Marinas" <catalin.marinas@gmail.com> writes:
>> > I noticed the weirdness few days ago and fixed it in
>> > e8813959aa3a7c41ffef61d06068b10519bd4830 (though no test caught it).
>> > Do you still see problems after this commit?
>>
>> The problem I see is that there still is no test case. That is bad and
>> means that it could break again tomorrow without anyone noticing.
>>
>> Luckily, I just wrote one for you :-)
>
> Thanks :-). We are still far from testing all the possible
> combinations. Is there a way to do code coverage in Python?

Being far from testing everything doesn't mean that you can't start adding tests for the things you know have a tendency to break. And for the things that you are going to refactor. And as regression tests when you fix a bug. A test suite can be built up by adding small parts at a time.

But no, I don't know of any useful code coverage tool for python, but I haven't really looked.

-- 
David Kågedal