Test program generation for functional verification of PowerPC processors in IBM
DAC '95 Proceedings of the 32nd annual ACM/IEEE Design Automation Conference
A study in coverage-driven test generation
Proceedings of the 36th annual ACM/IEEE Design Automation Conference
Symbolic Model Checking
Coverage-Directed Test Generation Using Symbolic Techniques
FMCAD '96 Proceedings of the First International Conference on Formal Methods in Computer-Aided Design
Specification-Based Test Generation for Security-Critical Systems Using Mutations
ICFEM '02 Proceedings of the 4th International Conference on Formal Engineering Methods: Formal Methods and Software Engineering
A generic micro-architectural test plan approach for microprocessor verification
Proceedings of the 42nd annual Design Automation Conference
ASP-DAC '03 Proceedings of the 2003 Asia and South Pacific Design Automation Conference
Abstractions for Model-Based Testing
Electronic Notes in Theoretical Computer Science (ENTCS)
Hi-index | 0.00 |
This paper describes the first application of the Genevieve test generation methodology. The Genevieve approach uses semi-for-mal techniques derived from “model-checking” to generate test suites for specific behaviours of the design under test. An “interest-ing” behaviour is claimed to be unreachable. If a path from an ini-tial state to the state of interest does exist, a counter-example is generated. The sequence of states specifies a test for the desired behaviour.To highlight real problems that could appear during test genera-tion, we chose the Store Data Unit (SDU) of the ST100, a new high performance digital signal processor (DSP) developed by STMi-croelectronics. This unit is specifically selected because of the fol-lowing key issues: big data structures that can not be directly modelled without state explosion, complex control logic that would require an excessive number of tests to exercise exhaustively, a design where it is difficult to determine how to drive the com-plete system to ensure a given behaviour in the unit under test.The Genvieve methodology allowed us to define a coverage model specifically devoted to covering corner cases of the design. Hence the generated test suite achieved very efficient coverage of corner cases, and checked not only functional correctness but also whether the implementation matched design intent. As a result the Genevieve tests discovered some subtle performance bugs which would otherwise be very difficult to find.