Expectations

In addition to instrumenting the source code with Test Points, defining the expectations based on the testing scenarios is required. The first step is defining the set of Test Points expected to be hit during a test. This is the list of Test Points and the expected number of hits for each of the Test Points. Also included is any expected data associated with a Test Point that requires validation.

Expected TEST POINTS list:

Label	Count	Expected Data
Name 1	1	<describe data payload validation requirements if applicable>
Name 2	1 +	<describe data payload validation requirements if applicable>
name ...	n	<...>

In addition to the list of Test Points certain processing properties are required to be defined.

Expected TEST POINTS processing properties:

Properties	Description
Ordered	Test Points are expected to be hit exactly as defined in the ordered list
Unordered	Test Points can be hit in any order defined in the list (only ordered or unordered can be set)
Strict	Test Points specified in the list must match exactly (i.e. no duplication)
Non-Strict	Test Points specified in the list can be duplicated during the processing (only strict or non-strict can be set)

An Unexpected Test Point list can also be defined. This list of Test Points are to be treated as failures if they are encountered.