On Tue, May 31, 2005 at 01:42:59PM -0400, Steven Rostedt wrote:
> How does one demonstrate that something works without a test. You may
> call it a "demo", but in reality it is just another test. It's been
> quite some time since I use to work on that, and I never read the
> MilSpec myself, I was just told what to do by those that did read it.
> But I would still call it testing. Every requirement must have a way to
> prove that it was fulfilled, whether it was by "demo", inspection, or
> measurement, I would call all those tests.
With testing I meant to run the OS on the bare hardware in the
final configuration and verifying that it works (possibly by measuring
the worst case latencies you get during the testing, like what Ingo does
to claim worst case latency for preempt-RT).
> One of the tests that were done was to inspect ever module (or function)
> for every code path it took. This grows exponential with every branch.
Yes, that's what I meant.
> the integration level, and system level. Could you imagine what it
> would take to do this with Linux! Linux is much bigger than that code
> that ran the engine of an aircraft, and that testing took ten years!
Indeed, that's why I believe hard-RT with preempt-RT is just a joke.
> Not to mention that Linux is a moving target, and the engine control
> code was designed for a single purpose and a single type of hardware.
Exactly.
> Before I put my hand under that saw, I would want to test it several
> times with a hotdog first!
;)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
