From: crm@duke.cs.duke.edu (Charlie Martin)
Subject: Re: Testing hidden subpgms and state data
Date: 4 May 88 17:36:58 GMT [thread overview]
Message-ID: <11685@duke.cs.duke.edu> (raw)
In-Reply-To: 8805041354.AA02809@boardwalk.mitre.org
One approach to testing that sort of hidden code I've used is to use a
source-level debugger to force a change in state that then exercises
the piece of code in question.
This was sort of a dreadful hack, but enabled us to test things that
couldn't readily be simulated in normal operation, e.g. error
condition handling during a power fail.
(Example: you have a power fail interrupt, the spec says to do
such-and-such on the power fail. You *could* test it for real by
installing it, enabling that interrupt, then pulling the plug. During
unit test, this tends to enrage the other 22 people using the machine.)
--
Charlie Martin (crm@cs.duke.edu,mcnc!duke!crm)
prev parent reply other threads:[~1988-05-04 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1988-05-04 13:54 Testing hidden subpgms and state data howell
1988-05-04 17:36 ` Charlie Martin [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox