MTest Project Protocol: MTest Demo EV3Control_ec Batch Project

MTest Project: MTest Demo EV3Control_ec Batch Project
MTest User: MTest Demo User
Generated at: 2019-10-29 09:48

Contents   [Requirement Catalog]   [Test Sequence Catalog]   [Signal Comparison Catalog]   [Assessment Catalog]   [Assessment Result Matrices]   [Test Project Protocol]


  1. Test Model: EV3Control_demo_ec
    1. Test Object: EV3Control
  2. Test Model: GlobalPosition_demo_ec
  3. Test Model: ManageVehicleStates_demo_ec
    1. Test Object: ManageVehicleStates
  4. Test Model: ObstacleDetection_demo_ec
  5. Test Project: All Passed Checks

1. Test Model: EV3Control_demo_ec    [Contents]

1.1 Test Object: EV3Control    [Contents]

Checks for Correctness — Fix This    [Contents]

     No issues found.

Checks for Completeness — Something Missing    [Contents]

CheckGuidelineResult CriteriaRecommended Actions
Assmnt_Completed:    Warning 

Scope:  Assessment is completed

Result Level:  TObj

Each assessment that is ready to be reviewed, should be marked as "completed".

Warning: An active assessment has not reached at least the status "completed".

Passed: All active assessments reached at least the status "completed".
  1. Open the assessment, and, after completion of the assessment, set the work status to "completed" (use button Open in the Evaluation/Assessment Result panel, to select an assessment, and set Assmnt.Status to 'complete').
    —OR—
  2. Open the Specification Editor and after completion of the assessment, set the status of the corresponding requirement to "completed" (use menu item Requirements and select MTest Assessable Requirements Syntax / Open Specification Editor, and set the field status to completed in the requirement definition).
9 Findings:
AssessmentTest Object Related Information
mars_REQ_EV3CTRL_011
Systemstart 1
EV3Control
EV3Control_demo_ec
Current work status:
created
mars_REQ_EV3CTRL_012
Systemstart 2
EV3Control
EV3Control_demo_ec
Current work status:
created
mars_REQ_EV3CTRL_021
Emergeny stop - stop or rev
EV3Control
EV3Control_demo_ec
Current work status:
created
mars_REQ_EV3CTRL_022
Emergeny stop - no steering
EV3Control
EV3Control_demo_ec
Current work status:
created
mars_REQ_EV3CTRL_031
Stop vehicle
EV3Control
EV3Control_demo_ec
Current work status:
created
mars_REQ_EV3CTRL_032
Stop vehicle
EV3Control
EV3Control_demo_ec
Current work status:
created
mars_REQ_EV3CTRL_041
x-Position no driving
EV3Control
EV3Control_demo_ec
Current work status:
created
mars_REQ_EV3CTRL_042
y-Position no driving
EV3Control
EV3Control_demo_ec
Current work status:
created
mars_REQ_EV3CTRL_05
y-Position no driving
EV3Control
EV3Control_demo_ec
Current work status:
created

Checks for Consistency — Double-Check    [Contents]

     No issues found.

Checks for Suggestions — Follow-Ups    [Contents]

     No issues found.

2. Test Model: GlobalPosition_demo_ec    [Contents]

3. Test Model: ManageVehicleStates_demo_ec    [Contents]

3.1 Test Object: ManageVehicleStates    [Contents]

Checks for Correctness — Fix This    [Contents]

     No issues found.

Checks for Completeness — Something Missing    [Contents]

CheckGuidelineResult CriteriaRecommended Actions
Assmnt_Completed:    Warning 

Scope:  Assessment is completed

Result Level:  TObj

Each assessment that is ready to be reviewed, should be marked as "completed".

Warning: An active assessment has not reached at least the status "completed".

Passed: All active assessments reached at least the status "completed".
  1. Open the assessment, and, after completion of the assessment, set the work status to "completed" (use button Open in the Evaluation/Assessment Result panel, to select an assessment, and set Assmnt.Status to 'complete').
    —OR—
  2. Open the Specification Editor and after completion of the assessment, set the status of the corresponding requirement to "completed" (use menu item Requirements and select MTest Assessable Requirements Syntax / Open Specification Editor, and set the field status to completed in the requirement definition).
10 Findings:
AssessmentTest Object Related Information
mars_REQ_MVS_01
Active state - VehicleControlOn
ManageVehicleStates
ManageVehicleStates_demo_ec
Current work status:
created
mars_REQ_MVS_02
Active state - VehicleControlOff
ManageVehicleStates
ManageVehicleStates_demo_ec
Current work status:
created
mars_REQ_MVS_031
Active state - VehicleIdle
ManageVehicleStates
ManageVehicleStates_demo_ec
Current work status:
created
mars_REQ_MVS_032
Active state - VehicleIdle
ManageVehicleStates
ManageVehicleStates_demo_ec
Current work status:
created
mars_REQ_MVS_04
Active state - EmergencyStop
ManageVehicleStates
ManageVehicleStates_demo_ec
Current work status:
created
mars_REQ_MVS_051
Autopilot activation/deactivation
ManageVehicleStates
ManageVehicleStates_demo_ec
Current work status:
created
mars_REQ_MVS_052
Autopilot activation/deactivation
ManageVehicleStates
ManageVehicleStates_demo_ec
Current work status:
created
mars_REQ_MVS_06
Forward movement
ManageVehicleStates
ManageVehicleStates_demo_ec
Current work status:
created
mars_REQ_MVS_07
Reverse movement
ManageVehicleStates
ManageVehicleStates_demo_ec
Current work status:
created
mars_REQ_MVS_08
No movement
ManageVehicleStates
ManageVehicleStates_demo_ec
Current work status:
created

Checks for Consistency — Double-Check    [Contents]

     No issues found.

Checks for Suggestions — Follow-Ups    [Contents]

     No issues found.

4. Test Model: ObstacleDetection_demo_ec    [Contents]

5. Test Project: All Passed Checks    [Contents]

Checks for Correctness — Fix This    [Contents]

CheckGuidelineResult CriteriaRecommended Actions
Assmnt_noErrors:    Passed 

Scope:  Assessment is executable

Result Level:  TProject

Assessments must run without leading to errors.

Errors in assessments can be caused by incorrect syntax, misspelled signals or parameter names, incorrect use of functions, signals of different length, and much more.

Failed: Assessment evaluation leads to an error on a test sequence.

Passed: All assessments run on all test sequences without errors occurring.
  1. Analyze the assessment with the test sequence that causes the error (select the test sequence in Execution panel, and use button Analyze in Evaluation/Assessment Result panel to choose and run the assessment.

CheckGuidelineResult CriteriaRecommended Actions
Assmnt_CheckedRegion:    Passed 

Scope:  Assessment is effective

Result Level:  TProject

An assessment must have an effective test region when using time tolerances.

Time tolerances can be observed via the return value "CheckedRegion" provided by many assessment helper functions.

A correctly used but empty "CheckedRegion" always indicates that a passed result has been achieved without actually testing the requirement.

Failed: Assessment result of a test sequence has a "CheckedRegion" as a vector of zeros.

Passed: All assessments have either a scalar "CheckedRegion" (not set by the user) or "CheckedRegions" with non-zero values.
  1. Analyze the assessment to look at triggered and checked regions as well as tolerances, and verify the assessment implementation (select a test sequence in Execution panel, and use button Analyze in Evaluation/Assessment Result panel to choose and run the assessment).

CheckGuidelineResult CriteriaRecommended Actions
Back2Back_noUnknowns:    Passed 

Scope:  Back-to-back data is available

Result Level:  TProject

Simulation data must exist for all signals in both simulation modes.

Missing data leads to the "Unknown" result.

It may indicate one of the following: the interface has changed or the test sequence has not been simulated in both simulation modes.

Failed: Back-to-back evaluation led to an "Unknown" result on a test sequence for the evaluated signal.

Passed: All back-to-back tests run on all test sequences without leading to an "Unknown" result.
  1. Simulate the test sequence in both simulation modes using the batch mode (use button Enter Batch Mode, select test sequence(s), check boxes of both simulation modes (right hand side), and press Start Batch Test)
    —OR—
  2. View corresponding test sequence report (use link in the finding list on right hand side).

Checks for Completeness — Something Missing    [Contents]

CheckGuidelineResult CriteriaRecommended Actions
TObj_ReqsImported:    Passed 

Scope:  Requirements are imported to test object

Result Level:  TProject

In requirements-based testing, requirements must be imported to each test object.

Requirements are the basis for the entire test process.

Warning: Test object has no respective requirements imported.

Passed: All test objects have a respective requirements imported.
  1. Import a requirements document file (use button Import in Requirements panel).

CheckGuidelineResult CriteriaRecommended Actions
TObj_TestableReqs:    Passed 

Scope:  Test object with testable requirements

Result Level:  TProject

When testing a test object the imported requirements should be testable.

Warning: A test object has imported requirements, but none of them are testable.

Passed: All test objects have at least one testable requirement imported.

This check will only apply to test objects that have requiremtents imported.
  1. Open the requirements management document, and double-check if the requirements are testable (use button Manage in the Requirements panel under Requirement).
    —OR—
  2. Open the requirement configuration, double-check the mask, and import again (use option Configure Requirements Import in the Requirements Menu).

CheckGuidelineResult CriteriaRecommended Actions
TObj_TSeqImported:    Passed 

Scope:  Test object has test sequences

Result Level:  TProject

Each test object should have test sequences.

Missing test sequences for a test object indicates that the test object has not been tested.

Warning: A test object does not have any test sequences.

Passed: All test objects have at least one test sequence.
  1. Assign a test sequence file (use button Assign in the Execution panel under Document).
    —OR—
  2. Create a new specification document (use button New in the Execution panel under Document) and import test sequences.
    —OR—
  3. Create a new test group (use button Add in the Execution panel under Test Group) and repeat the actions above.

CheckGuidelineResult CriteriaRecommended Actions
Req_DescriptionNotEmpty:    Passed 

Scope:  Testable requirement has a description

Result Level:  TProject

Each testable requirement should have a description.

Failed: A requirement does not have a description.

Passed: All requirements have a description.

  1. Open your requirements file and provide a proper description (use option View Requirements Document in the Requirements menu). Do not forget to re-import afterwards.

CheckGuidelineResult CriteriaRecommended Actions
Req_Evaluated:    Passed 

Scope:  Requirement Evaluation

Result Level:  TProject

Each testable requirement must show an evaluation result.

The result is aggregated from linked assessments and from linked test sequences. The test sequence result is obtained from back-to-back test, regression test, or manual evaluation.

A missing evaluation result indicates an untested requirement.

Failed: Requirement is testable, but no evaluation result is available (aggregated results from regression test, back-to-back test, or manual evaluation of linked test sequences and results of linked assessment).

Passed: Evaluation result is available for each testable requirement, aggregated from results of linked test sequences and/or assessments.
  1. Check existing test sequences for missing requirement links (see TSeq_ReqsLinked), and add requirement ID (use button Edit in Execution panel under Test Sequence, and add ID in test sequence under Requirements)
    —OR—
  2. Create a new test sequence that stimulates the requirement, and associate it with the related requirement ID (use button Edit in Execution panel under Test Sequence, and set ID in test sequence under Requirements)
    —OR—
  3. Check existing assessments for missing requirement links (see Assmnt_ReqsLinked), and add requirement ID (use button Open in Evaluation/Assessment Result panel, and add ID in assessment under Assmnt.ReqIDs)
    —OR—
  4. Create a new assessment that observes the requirement, and associate it with the related requirement ID (use button Add in Evaluation/Assessment Result panel)
    —OR—
  5. Activate automatic evaluation (use button Configure in Evaluation panel), and evaluate test sequences
    —OR—
  6. If no automatic evaluation is favored, set at least a manual evaluation result for linked test sequence.

CheckGuidelineResult CriteriaRecommended Actions
Req_Reviewed:    Passed 

Scope:  Requirement testability review

Result Level:  TProject

The requirement and its testability status should be reviewed and confirmed by the tester.

Requirements that were not reviewed and are unintentionally marked as not testable will be mistakenly ignored during the test process.

Warning: Requirement does not have the status "reviewed".

Passed: All requirements have a "reviewed" status.
  1. Open the requirement management dialog, and set testability review status - after the review - to "reviewed" (use button Manage in Requirements panel).

CheckGuidelineResult CriteriaRecommended Actions
TSeq_NameNotEmpty:    Passed 

Scope:  Test sequence has a name

Result Level:  TProject

Each test sequences should have a name.

Warning: A test sequence does not have a name.

Passed: All test sequences have a name.

  1. Open your test sequence description file and provide a name for the test sequence (select the respective test sequence and then use the button Edit in the Execution panel). Do not forget to re-import afterwards.

CheckGuidelineResult CriteriaRecommended Actions
TSeq_DescriptionNotEmpty:    Passed 

Scope:  Test sequence features a description

Result Level:  TProject

Each test sequence should have a description.

Descriptions of test sequences faciliates review and maintainability

Warning: A test sequence does not have a description.

Passed: All test sequence have a description.

  1. Open your test sequence description file and provide a proper description for the test sequence (select the respective test sequence and then use the button Edit in the Execution panel). Do not forget to re-import afterwards.

CheckGuidelineResult CriteriaRecommended Actions
TSeq_Reviewed:    Passed 

Scope:  Test sequence is reviewed

Result Level:  TProject

Each test sequence should be reviewed.

Reviewing test sequences is good practice for assuring high quality of functionality and documentation.

Warning: A test sequence has not reached the status "reviewed".

Passed: All test sequences reached the status "reviewed".
  1. Open the test sequence and - once reviewed - set its work status to "reviewed" (use button Edit in the Execution panel, and in the column MTCD Work Status set the work status to "reviewed").

CheckGuidelineResult CriteriaRecommended Actions
TSeq_ReqChanged:    Passed 

Scope:  Automatic status "reqchanged" in test sequence

Result Level:  TProject

A test sequence should be revisited after the linked requirements have been changed.

Revisiting test sequences after requirements change is good practice for assuring the sequence still stimulates its linked requirements correctly.

Warning: The status of a test sequence was set to "reqchanged".

Passed: No test sequences have the status "reqchanged".
  1. Open the test sequence and check if the requirement change requires an adaption of the test sequence (use button Edit in the Execution panel).

CheckGuidelineResult CriteriaRecommended Actions
TSeq_IfChanged:    Passed 

Scope:  Automatic status "ifchanged" in test sequence

Result Level:  TProject

A test sequence should be revisited after the interface has been changed.

Revisiting test sequences after an interface change is good practice for assuring the sequence stimulates the interface as before.

Warning: The status of a test sequence was set to "ifchanged".

Passed: No test sequences have the status "ifchanged".
  1. Open the test sequence and check if interface change requires an adaption of the test sequence (use button Edit in the Execution panel).

CheckGuidelineResult CriteriaRecommended Actions
TSeq_EvalResultAvailable:    Passed 

Scope:  Test sequence evaluation

Result Level:  TProject

A test sequence should be evaluated with regard to all of its configured evaluation method(s).

Test sequences that not have been evaluated provide no test result.

Warning: A test sequence has not been evaluated or is missing some evaluation results.

Passed: All test sequences have been evaluated for all configured evalustion methods.
  1. Simulate the test sequence and perform evaluation afterwards (use button Simulate in the Execution panel followed by using the button Perform in the Evaluation panel).
    —OR—
  2. Perform evaluation for the test sequence (use button Perform in the Evaluation panel).
    —OR—
  3. Check your evaluation configuration(s) (use button Configure in the Evaluation panel).

CheckGuidelineResult CriteriaRecommended Actions
TSeq_AssmntsEvaluated:    Passed 

Scope:  Test sequences with evaluated assessments

Result Level:  TProject

An active assessment should be evaluated.

A missing evaluation result of an assessment indicates an untested requirement.

Warning: Assessment is active, but has no evaluation data.

Passed: All active assessments have evaluation data.
  1. Evaluate the listed test sequences (use button Perform in Evaluation Panel).
    —OR—
  2. Set non evaluated assessment inactive (use button Open in Evaluation/Assessments Results Panel and set Assmnt.Active to 0 in .m-file).

CheckGuidelineResult CriteriaRecommended Actions
Assmnt_NameNotEmpty:    Passed 

Scope:  Assessment has a name

Result Level:  TProject

Each assessment should have a name.

Warning: An assessment does not have a name.

Passed: All assessments have a name.

  1. Open the assessment, and give it a name (use button Open in Evaluation/Assessment Result panel, and add name in assessment under Assmnt.Name).
    —OR—
  2. Open the Specification Editor and give the corresponding requirement a name (use menu item Requirements and select MTest Assessable Requirements Syntax / Open Specification Editor, and add a name under the field name in the requirement definition).

CheckGuidelineResult CriteriaRecommended Actions
Assmnt_DescriptionNotEmpty:    Passed 

Scope:  Assessment has a description.

Result Level:  TProject

Each assessment should have a description.

A description is important for understanding the assessment.

Warning: An assessment does not have a description.

Passed: All assessments have a description.

  1. Open the assessment and give a description (use button Open in the Evaluation/Assessment Result panel, and add description in assessment under Assmnt.Description).

CheckGuidelineResult CriteriaRecommended Actions
Assmnt_ReqChanged:    Passed 

Scope:  Automatic status "reqchanged" in assessment

Result Level:  TProject

An assessment should be revisited after the linked requirements have been changed.

Revisiting assessments after a change of requirements is good practice for assuring the assessment still resembles the requirement.

Warning: The status of an assessment was set to "reqchanged".

Passed: No assessments have the status "reqchanged".
  1. Open the assessment and check if the requirement change requires an adaption of the assessment (use button Open in the Evaluation/Assessment Result panel and select a corresponding assessment).
    —OR—
  2. In case of an assessment automtically generated by MARS, open the Specification Editor and check if rework due to changed requirements is needed (use menu item Requirements and select MTest Assessable Requirements Syntax / Open Specification Editor).

CheckGuidelineResult CriteriaRecommended Actions
Assmnt_IfChanged:    Passed 

Scope:  Automatic status "ifchanged" in assessment

Result Level:  TProject

An assessment should be revisited after the interface has been changed.

Revisiting assessments after an interface change is good practice for assuring the assessment still resembles the requirement.

Warning: The status of an assessment was set to "ifchanged".

Passed: No assessments have the status "ifchanged".
  1. Open the assessment and check if the interface change requires an adaption of the assessment. (use button Open in the Evaluation/Assessment Result panel and select a corresponding assessment).
    —OR—
  2. In case of an assessment automtically generated by MARS, open the Specification Editor and check if rework due to changed interface is needed (use menu item Requirements and select MTest Assessable Requirements Syntax / Open Specification Editor).

CheckGuidelineResult CriteriaRecommended Actions
Assmnt_Triggered:    Passed 

Scope:  Assessment is triggered

Result Level:  TProject

An assessment must show a "Passed" or "Failed" aggregated evaluation result.

This only occurs if an assessment is triggered by at least one test sequence.

A non-triggered assessment indicates that either the implementation of the related requirement is incorrect or that there are no test sequences to stimulate the assessment correctly.

Failed: Assessment has an aggregated "NotTriggered" result for all test sequences of the corresponding test object.

Passed: All assessments have a "Passed" or "Failed" result for at least one test sequence of the corresponding test object.
  1. Open or analyze the assessment to look at triggered and checked regions as well as tolerances, and verify the assessment implementation (select a linked test sequence in Execution panel, and use buttons Open/Analyze in Evaluation/Assessment Result panel to choose and run the assessment.)
    —OR—
  2. Create a new test sequence (use button Edit in Execution panel under Test Sequence.).

Checks for Consistency — Double-Check    [Contents]

CheckGuidelineResult CriteriaRecommended Actions
Req_LinkedTSeqs:    Passed 

Scope:  Requirement linked in test sequences

Result Level:  TProject

A testable requirement should be stimulated by at least one specific test sequence.

A missing link between requirements and test sequences indicates that stimulating these requirements has not been sufficiently considered.

Warning: Requirement is testable, but its ID is not linked in any test sequence for this test object.

Passed: Requirement ID is linked in at least one test object’s test sequence.
  1. Check existing test sequences for missing requirement links (see TSeq_ReqsLinked), and add requirement ID (use button Edit in Execution panel under Test Sequence, and add ID in test sequence under Requirements)
    —OR—
  2. Create a new test sequence that stimulates the requirement, and associate it with the related requirement ID (use button Edit in Execution panel under Test Sequence, and set ID in test sequence under Requirements).

CheckGuidelineResult CriteriaRecommended Actions
Req_LinkedAssmnts:    Passed 

Scope:  Requirement linked in Assessment

Result Level:  TProject

Using assessments for evaluation, a testable requirement should be observed by at least one specific assessment.

A missing link between requirements and assessments indicates that the related requirements are not tested.

Warning: The requirement is testable, but its ID is not linked in any of this test object’s assessment.

Passed: Requirement ID is linked in at least one of the test object’s assessments.

This check will only apply to test objects that have at least one test sequence with assessment evaluation configured.
  1. Check existing assessments for missing requirement links (see Assmnt_ReqsLinked), and add requirement ID (use button Open in Evaluation/Assessment Result panel, and add ID in assessment under Assmnt.ReqIDs)
    —OR—
  2. Create a new assessment that observes the requirement, and associate it with the related requirement ID (use button Add in Evaluation/Assessment Result panel).

CheckGuidelineResult CriteriaRecommended Actions
TSeq_ValidID:    Passed 

Scope:  Test sequence has valid ID

Result Level:  TProject

A test sequence should have a valid ID.

Unique IDs for test sequences are important for traceability.

Warning: Test sequence ID is empty or exists multiple times.

Passed: All test sequences show a valid ID.
  1. Open the test sequence document, and provide unique IDs for all test sequences (use button Edit in the Execution panel under Test Sequence, and check the IDs under TestID). Do not forget to re-import the test sequences afterwards.

CheckGuidelineResult CriteriaRecommended Actions
TSeq_ReqsLinked:    Passed 

Scope:  Test sequence linked to requirement

Result Level:  TProject

A test sequence should link at least one requirement.

The link between test sequence and requirement is important for traceability in the test process.

Warning: Test sequence has no linked requirement.

Passed: All test sequences have at least one linked requirement.
  1. Open the test sequence document, and associate the sequence with the related requirement ID (use button Edit in Execution panel under Test Sequence, and set ID in test sequence under Requirements).

CheckGuidelineResult CriteriaRecommended Actions
TSeq_ManEval:    Passed 

Scope:  Test sequence is manually evaluated

Result Level:  TProject

Manual results need to be revised to verify the correctness of their use.

Warning: A test sequence evaluation result has been overruled.

Passed: All test sequences have automatic evaluation result only.
  1. Check existing test sequences for correct use of manual results.
    —OR—
  2. In case of improper use: Delete the manual evaluation data (use menu item Evaluation and select Manual Evaluation, use button Delete for the selected test sequence).

CheckGuidelineResult CriteriaRecommended Actions
Assmnt_ReqsLinked:    Passed 

Scope:  Assessment linked to requirement

Result Level:  TProject

An assessment should link at least one requirement.

A link between assessment and requirement is important for traceability in the test process.

Warning: Assessment has no linked requirement.

Passed: All assessments have at least one linked requirement.
  1. Open the assessment and associate it with the related requirement ID (use button Open in Evaluation/Assessment Result panel, and add ID in assessment under Assmnt.ReqIDs).

Checks for Suggestions — Follow-Ups    [Contents]

CheckGuidelineResult CriteriaRecommended Actions
Assmnt_Active:    Passed 

Scope:  Assessment is active

Result Level:  TProject

In general, an assessment should be active.

Inactive assessments are not part of the evaluation.

Information: An assessment is not active.

Passed: All assessments are active.

  1. Open the assessment, and set the active status to true (use button Open in theEvaluation/Assessment Result panel, select the respective assessment, and, in the assessment m-file, set Assmnt.Active to true).

CheckGuidelineResult CriteriaRecommended Actions
Assmnt_notFailed:    Passed 

Scope:  Failed assessment

Result Level:  TProject

In general, assessments with a "Failed" result indicate incorrect behavior of the test object.

The tester should focus on failed assessments to assure correct implementation regarding the requirements.

Information: Assessment evaluation shows a "Failed" result on a test sequence.

Passed: All assessments run on all test sequences without leading to a "Failed" result.
  1. Analyze the assessment to look at triggered and checked regions as well as tolerances, and verify the assessment implementation (select the test sequence in Execution panel, and use button Analyze in Evaluation/Assessment Result panel to choose and run the assessment).

CheckGuidelineResult CriteriaRecommended Actions
Back2Back_notFailed:    Passed 

Scope:  Failed back-to-back tests

Result Level:  TProject

In general, back-to-back tests with a "Failed" result indicate incorrect behavior of the test object.

The tester should focus on failed back-to-back tests to assure correct simulation data and tolerances.

Information: Back-to-back test shows a "Failed" result on a test sequence.

Passed: All back-to-back tests run on all test sequences without leading to a "Failed" result.
  1. Check tolerances (use menu Evaluation/Configure Signal Tolerance)
    —OR—
  2. View corresponding test sequence report (use link in the finding list on right hand side).