[openbeosnetteam] Re: Tests plan?

It seems we may be able to formalize a testing group as well.  Scott
and I for sure, and perhaps Waldemar.  If we have a definite set of
testers, we can work together to create the test plans and so on.

I think our first step should be some informal testing, to get a
general idea of what works and what doesn't.  Also, I don't think
duplication is a big deal at this point and with such a small group. 
I think it's a good thing right now, actually.

I personally am testing the stack initially by running through each
of our available network applications:

arp
ifconfig
ping  
route
traceroute

I am not testing pppconfig, but I think Waldemar is.  I am writing up
informal test plans for each command, so I can keep track of what I
am doing.  As I stated in my email (subject: My Personal Project
page), I will be posting everything I do to http://www.new-wisdom.com
for everyone to view.

Once we get past this first stage, I am will to right up formal test
plans so we can dig further into the issues and start changing code...

I have some other ideas as well, but what do you all think of this so
far?

Brennan

---- Original Message ----
From: philippe.houdoin@xxxxxxx
To: openbeosnetteam@xxxxxxxxxxxxx
Subject: RE: [openbeosnetteam] Tests plan?
Date: Fri,  9 Jan 2004 16:27:42 +0100

>Hi guys.
>
>I'm overloaded by my pending PhD grade duties since monday, but I
>hope being 
>able to slow down during week-end.
>Anyway, I' happy to see multiple stacks testers :-)
>
>Maybe it's time to put down some tests plan?
>IIRC, we do have some old testing code lying in
>current/src/tests/net, that 
>we can relive.
>Another points is to put down on a list all issues we already knows
>about 
>the stack, libnet.so DNS bug coming to mind but I'm sure you have
>yours too.
>
>I'm not used to tests plan. but I feel putting it right will make
>such thing 
>reusable and usefull for non-regression tests in the future.
>
>What do you think? Any tests plan pro here ? ;-)
>
>- Philippe, busy-in-real-life team leader.
>

Other related posts: