[openbeosnetteam] Re: Tests plan?

Hey Gang,

On Jan 9, 2004, at 9:03 AM, Brennan Cleveland wrote:

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.

Based on what's been posted in the past I think that Waldemar is the only one who can exercise the PPP stuff (?). I, for one, cannot test this because I have an ADSL connection with a static IP address.

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 also think we should capture a core dump on Philippe's and Waldemar's brain. You and I are coming into this cold (which has its advantages), but a quick proverbial "state of the union address" definitely couldn't hurt.

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

arp
ifconfig
ping
route
traceroute

How about more abusive things like nmap (or the Be equivalent), ping floods, and multicast?

Do we have a way to test things like IGMP or PIM? What about UDP?

In this age where "internet security" seems to be the buzzword du jour, Be lacks anything even remotely resembling stateful packet filtering. Sorry, that's the security freak in me rearing its ugly head. Is this applicable to R5, or GE stuff? Nathan, do you have anything to add here?

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...

Hmmmm... Seems to me that the "first stage" you propose is an artificial milestone. After all, the stack and its kith and kin, have been under development for some time now. I'd rather step back and take in the bigger picture, fix what's broken, and evolve the product (pardon the corporate-speak).

I have some other ideas as well,

Share! :-)

but what do you all think of this so far?

Grade A. The more eyes the better. Thank you for your efforts!

Brennan 

Cheers,
Scott "perhaps a little too pedantic" Mansfield


---- 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: