Crash Test Team
Submitted by smartini on Mon, 06/07/2004 - 16:48.
Hi to all,
anyone is interested in the creation of a Team to Test the Robustness of the System in many ways ? A New Generation System like this must be Projected/Tested having also these features in mind.
I think we should try to damage/force JNode in many ways as soon as the Project evolves. With manual and automatic Unit/System Tests.
From Java Components/Applications/Drivers , but also from other machines (Ping-Of-Death, Buffer Overflow, Viruses, SpyWare, accidental deletion of critical files, simulate critical files corruption, etc. ... ) every day some new attack become real.
Bye,
Sandro
- Login to post comments
I agree
As I said before, we really need Unit tests and also others kind of test s as you say.
Several weeks ago, I wrote unit tests for JNode-FS but it's very hard to write this kind of tests. This need some context stuff (hard drive, OS like linux or NT or Windows 9*, hard drive partition) and hardware/driver aren't pure software so we need to adapt the tests to this fact.
However, as Ewout suggested, I think developers shouldn't be testers (but should do unit tests) because they have knowledge about their code and have tendencies (not volontary) to better test the well working part than the other parts.
Fabien
I agree
Hi,
I agree that we need such tests.
Many of us tested JNode and found a lot of things to do.
In addition I prefer testing JNode in a working manner, because these demage attacks will be not our problem in the next two or three month.
It is more important to use this team to proof that JNode can run the given code correct. (e.g. driver, filesystems and so on)
Trickkiste
Great idea
I think this is a great idea which I fully support. I'll not be part of that team, since I'm a big contributor of sourcecode, but I'll be very glad to help make this possible.
Ewout