27.07.2013 Views

2 Why We Need Model-Based Testing

2 Why We Need Model-Based Testing

2 Why We Need Model-Based Testing

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

318 Glossary<br />

compound value. An N<strong>Model</strong> data type which is a value type that can handle<br />

tree-structured and variable-length data. The N<strong>Model</strong> data types set, map, sequence,<br />

value array, and bag derive from compound value.<br />

concurrent system. A system where more than one program runs at a time. Multithreaded<br />

programs and distributed systems are examples of concurrent systems.<br />

conform. Tobeinconformance.<br />

conformance. Agreement between an implementation and a model program.<br />

conjunction. An expression that contains the and operator, && in C#. Contrast to<br />

disjunction.<br />

contract model program. Amodel program intended to act as a specification.<br />

Contrast to scenario model program.<br />

control state. The part of the state that determines which actions are enabled. The<br />

state variables that appear in enabling conditions. Contrast to data state.<br />

control structure. Code that controls which statements are executed and in which<br />

order. In model programs, control structure is replaced by enabling conditions.<br />

controllable action. Anaction that can be invoked under the control of a test<br />

harness. Also called tester action. Contrast to observable action.<br />

cover. To visit a coverage point by exercising some program part or property.<br />

coverage. A measure of how much testing has been done.<br />

coverage point. A part or property of a program used to measure coverage, by<br />

counting how many times it is executed, visited, or otherwise exercised. A state, an<br />

action, or a branch in the code could be a coverage point. A strategy can use coverage<br />

points. In the N<strong>Model</strong> framework, coverage points are represented by terms.<br />

current state. The state before a transition.<br />

cycle. A loop in a graph. A cycle in an FSM indicates repetitive behavior and might<br />

indicate a livelock.<br />

data abstraction. Abstraction applied to variables. A higher level of data abstraction<br />

uses fewer variables, fewer values for those variables, and simpler data types.<br />

data state. The part of the state that does not determine control flow. Contrast to<br />

control state.<br />

dead state.Astate from which an accepting state cannot be reached. A system that<br />

reaches a dead state experiences a liveness failure. Dead states indicate deadlocks<br />

or livelocks.<br />

deadlock. Aliveness failure where a program stops executing because it reaches a<br />

state where no actions are enabled.<br />

more free ebooks download links at:<br />

http://www.ebook-x.com

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!