Definition

A stuck-at-fault is a fault-analysis concept used at the circuit-design level. The provided source describes stuck-at-faults as a common analysis technique in which a given circuit design—an implementation—is modified by mutators that capture a fabrication fault model. An example fault model is that one or more wires connecting gates in the circuit are broken. [Definition and fault model]

Testing characterization

The source characterizes stuck-at-fault analysis as conceptually similar to a white-box mutation technique, because the testing activity modifies or reasons over the structure of the implementation. As an implementation-based testing method, it has the corresponding advantages and drawbacks when compared with specification-based approaches. [White-box and implementation-based characterization]

Effectiveness

Stuck-at-fault techniques are described as very effective for medium-size circuits. They use the structure of the given design to construct equivalence-class tests that directly incorporate a fault model. [Effectiveness for medium-size circuits]

Limitations

The same source notes that this kind of testing will not reveal certain design flaws, giving as an example a write-read error under the influence of byte alignments in memory. [Limitation: design-level flaws]

Context in microprocessor test generation

In the cited VAMP microprocessor case study, the authors state that they had a VAMP gate-level model and could have selected a testing technique at that level, but instead chose to stay at the design level of the VAMP machine. They also note that equivalence classes could be refined further by exploring byte-level or bit-level representations of registers and memory cells. [VAMP testing-methodology context]