[htdig-dev] Testing Tasks

[Neal R. <ne...@ri...>]

Hey all,
	I used Lachlan's break down (nearly unchanged) to create 19
testing tasks @ Soureforge.

Please visit http://sourceforge.net/projects/htdig/ and navigate to
Tasks-> Testing 3.2

Some of them are fairly long, some are short.

I'm not assigning any to anyone, it's up to each of us to grab a task and
complete it.  I'm also leaving it up to each person to decide how deep to
test.  We need to get reasonable coverage.

I would also encourage each of you to use valgrind to check for memory
leaks while you are testing. Again, the depth you go looking for them is
up to you.
http://developer.kde.org/~sewardj/

If you need a Sourceforge account, please register yourself and send me an
email with your account and I'll add you to the htDig project.

If you find an error during testing please:
1)Create a bug
2)Contact appropriate developer or fix it yourself
3)Test fix
4)Commit fix (if you are fixing it)
5)Update status of bug
6)Have a second person either test fix or verify that commited
  code looks OK.. their choice.

So the standards for release of 3.2RC1 are:
1) No important bugs in 'Include_in_3.2' queue
2) All testing tasks completed.

Sourceforge is very cool!

Thanks all!

Neal Richter
Knowledgebase Developer
RightNow Technologies, Inc.
Customer Service for Every Web Site
Office: 406-522-1485