> Philip Hands <[EMAIL PROTECTED]> took the time to put together a simple perl
> script that does this and packaged it into a program called debian-test.
> As you can tell by the version number, it's just something to get us
> started with, wishlist bugs are welcome.
There is a 0.0.2 version on it
On 09-Nov-98, 11:07 (CST), Daniel Martin <[EMAIL PROTECTED]> wrote:
> I will repeat my suggestion (since when I first made it, it was in a
> parenthetical comment and I wasn't quite certain what I meant by it
> anyway) for a "List of fixed bugs" to be included either under
> /usr/doc// or at the v
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> Let us see how relevant this is Here are my list of resolved
> bugs. Let us see..
>
> 29 bug reports.
>2 cases whre reproducers were possible, one whereit is available
>6 possible test, with 3 being noted as tricky
> 23 cases where
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> Hi
> >>"Raul" == Raul Miller <[EMAIL PROTECTED]> writes:
> Raul> I'm not talking about a complete regression test suite here.
> Raul> I'm talking about simple test cases. If the code dumps core
> Raul> under some condition, reproduce the conditio
Hi
>>"Raul" == Raul Miller <[EMAIL PROTECTED]> writes:
Raul> Manoj Srivastava <[EMAIL PROTECTED]> wrote:
>> Writing regression tests for real is a hard, painstaking effort,
>> often requiring intimate knowledge of the code, and often needs to be
>> tied up with the code itself, changing as the
On 8 Nov 1998, Adam Di Carlo wrote:
> >> The debian-testing group is actually working on this issue as well,
> >> someone should liase with them.
> > Agreed. But I'm at a loss here -- I don't see a debian-testing
> > mailing list, and I don't see any testing links off of the
> > developer's corn
In article <[EMAIL PROTECTED]>, Raul Miller <[EMAIL PROTECTED]> writes:
> Adam Di Carlo <[EMAIL PROTECTED]> wrote:
>> Raul, I really think the proof is in the pudding. If you can help
>> shape a working, easy enough to manage test suite, and start
>> filling that in (even, just start with base pack
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> Writing regression tests for real is a hard, painstaking effort,
> often requiring intimate knowledge of the code, and often needs to be
> tied up with the code itself, changing as the source changes.
I'm not talking about a complete regression test
Hi,
I have a package where I wrote a test suite. It is
pkg-order. I think I spent about a fifth of the total time creating
the package in writing the test suite. I don't think I could have
written the tests had I not also been the author of the package.
Writing regression test
Adam Di Carlo <[EMAIL PROTECTED]> wrote:
> Raul, I really think the proof is in the pudding. If you can help
> shape a working, easy enough to manage test suite, and start filling
> that in (even, just start with base packages), we'll be able to look
> at it from there and decide if there's a polic
In article <[EMAIL PROTECTED]>, Raul Miller <[EMAIL PROTECTED]> writes:
> Adam Di Carlo <[EMAIL PROTECTED]> wrote:
>> Raul has suggested to add test cases to debian/rules to certify
>> that a bug is gone. As much as I think our documentation should
>> encourage maintainers to write test cases, I be
Daniel Martin <[EMAIL PROTECTED]> wrote:
> Perhaps a "checklist" of manual tests for bugs combined with an
> automated script to check for bugs that can be tested that way (Hmm -
> perhaps a strongly suggested /usr/doc//bugfixlist ?) might be
> an option, but really I'd just prefer to rely on maint
Adam Di Carlo <[EMAIL PROTECTED]> wrote:
> Raul has suggested to add test cases to debian/rules to certify that
> a bug is gone. As much as I think our documentation should encourage
> maintainers to write test cases, I believe this puts undue stress
> on package maintainers. Moreover, if we do not
Adam Di Carlo <[EMAIL PROTECTED]> writes:
> Raul has suggested to add test cases to debian/rules to certify that a
> bug is gone. As much as I think our documentation should encourage
> maintainers to write test cases, I believe this puts undue stress on
> package maintainers. Moreover, if we do
Raul has suggested to add test cases to debian/rules to certify that a
bug is gone. As much as I think our documentation should encourage
maintainers to write test cases, I believe this puts undue stress on
package maintainers. Moreover, if we do not have the cooperation of
the upstream maintain
15 matches
Mail list logo
