[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [DotGNU]DotGNU testing standards
From: |
Rhys Weatherley |
Subject: |
Re: [DotGNU]DotGNU testing standards |
Date: |
Wed, 09 Jan 2002 16:03:30 +1000 |
Dave Manning wrote:
> I don't want to coem
> back and report, "errr...Rhys, your application crashed." I think it
> would be far better if I could report back, "Rhys, process line 5364
> produces a stack crash during system condition XXX 34% of the time."
I agree.
> Moreso, to have simplicity for the developer, for me and for any other
> testers we get, I'd like to have a semi-standardized testing methodology
> available along with the necessry tools to test and measure dotGnu code
> under development. I'm still searching for tools and methods to use,
> have found a few, but would very much like the developer inputs on this.
Have you looked at the HACKING file for pnetlib?
It's oriented towards contributing developers, but does
contain some information on setting things up for tests.
I can add more information on testing, bug reporting, etc.
Or would you find it better if I created a separate
TESTING file?
My plan is to have HACKING file for each major
component to assist incoming developers and testers.
It will take a few weeks to get this in place though.
Of course, this doesn't necessary solve the "tools and
methods" problem. Testing tools and methods aren't
necessarily my forte. Tell me what you need, and I'll
add it to the HACKING files.
I would also like to see a formal bug management policy
develop. We had a pretty nice bug system at a previous
company that I worked for. I'll post separately on that.
Cheers,
Rhys.