APPENDIX A
Diagnostic Profiler Provisions
The following paragraphs provide an overview of the provisions in the Diagnostic Profiler for
developing a Diagnostic Knowledge Base for Windows applications. Further details can be found in
the Diagnostic Profiler User Manual.
A.1 Defining Tests
In using the Diagnostic Profiler, you define the test routines that will be applied to the UUT. In defining
these test routines, you define the specific points, or locations, in the circuit that are covered by a test.
(This relates to the "Effected Test Points" column in the "Test Specifications" window.)
A.2 Defining Test Coverage
Associated with each test location in the Effected Test Points column are a
number of "Causes" which
relate to the signal path associated with a test location. If the functionality any of those locations listed
in the cause list are not verified by the test, then they should be "turned off." (Highlight the items in the
Causes list and Press No.) If the functionality of any of those locations listed in the cause list are only
partially verified by the test, then they should be assigned as "Partial." When defining a test as partially
covering a specific location, you are presented with a scroll bar. The value of this scroll bar is not
relevant. The number is used to indicate situations where two different tests partially cover the same
functionality of the same location.
A.3 Define Test Executable Name
Associated with each defined test is a linkage to the execution of that test. This is done so that the
Diagnostician can call a test program to be executed so that it can get the test results it needs to derive
a diagnosis or to reduce the ambiguity group.
The name of the executable program associated with a test is defined in the Test Specifications Windows
under the Executable field. (Select Define Tests from main Profiler screen.)
A.4 System Test
In the "Show System" Window
of the Profiler is a field for the System Test. This field represents the
primary (end-to-end) test that is to be run upon start of the test procedure. The test program name
should be entered here.
A.5 Test Results
Not Required for Windows-based applications, as test results are passed via DDE-mediated
conversations from the LabView application.
A.6 Test Program Provisions
A.6.1 Generate Test Results (File) and Pass Test Results Data
The test program must be capable of generating test result data which is meaningful to the
Diagnostician. The test results must be passed to the Diagnostician via DDE messages described
earlier. The syntax for passing test results to the Diagnostician is as follows:
[TEST NAME] Must be identical to test name defined in
Diagnostic Profiler
TEST_LOCATION=P/F/R;
TEST_LOCATION=P; indicate that a test passed
TEST_LOCATION=F; to indicate that a test failed
TEST_LOCATION=R; to indicate that a the execution of the test
was not performed (refused by the operator)
or were insufficient to categorize the test
as pass or fail. This forces the run-time
to not ask forexecution of that module again.
In order for the test results to be meaningful to the Diagnostician, they must correspond to the
information set-up in the Diagnostic Knowledge Base as follows:
The TEST NAME must have a one-to-one correspondence with the name of the test as defined in the
DEFINE TESTS screen in the Diagnostic Profiler. It must be enclosed in square brackets ([...]).
The TEST_LOCATION must have a one-to-one correspondence with the Effected Test Points defined
in the Profiler in the middle column of the Define Tests window.
NOTE: Neither the TEST NAME nor the TEST_LOCATION are necessarily the name of the
executable test routine from the run-time linkages section of the Profiler Define Tests screen.
| 
