-
Notifications
You must be signed in to change notification settings - Fork 0
FormalTest
Ben Christel edited this page Jun 12, 2022
·
1 revision
A formal test describes a desirable Interaction between a Component and its Collaborators in algorithmic (executable) language. Running a formal test demonstrates whether the interaction is a member of the component's Behavior.
A formal test describes an Interaction by:
- partitioning the Components involved into a TestSubject and Collaborators
- simulating an interaction between the TestSubject and its collaborators, usually by playing the role of one collaborator and sending messages to the TestSubject as if it were that collaborator, or by using TestDoubles.
"Formal" means the test has unambiguous preconditions, steps, and postconditions. Because a formal test places unambiguous requirements on the TestSubject, it can signal a pass/fail result.
A FormalTest can be either Automated or Manual. It can be a UnitTest or a SystemTest.