naming
[email protected]
NAMING
.tdf = the test
.abs = the build
.alb = the library
.bd = bus define file
.ct = correlation table file
.inc = include file
.ssi = dapped test
.res = test results
.rpt = report file (formatted test results)
.pth = path file
.ptl = list of path files
.xin = execution file
.xil = list of execution files
.cul = list of code procedures to cover
.tcr = coverage report
.tce = coverage report with excuses
.tcb = detailed coverage report
.dis = disassembly file
.exc = exception file (for failures)
.tfl = list of files to run in batch
.trc = trace matrix input file
.ins = inspection file
INSPECTION FILES
1. For initial development of TDFs, the following inspection naming
convention will be used by the FPD SW Test team.
.ins
2. For SCR rework after the initial development, the following inspection
naming convention will be used by the FPD SW Test team.
.ins
In this naming convention for SCR rework inspections, the first three
letters (AAA) represent the functional area, the next 8 digits (SCRNO_XX)
represent the SCR No. including the split suffix, and the remaining
characters (YYYYYYYYYYYYYYYYY) are optional, but may be used to represent
the subfunction addressed by the SCR. The total number of characters used
in the name probably should not exceed 31, although the SCR field for
entering an element name accepts up to 43 characters. We will standardize
on using a 5 character SCR number plus a 2 digit suffix to allow numbering
up to 99999.99.
NAMING
if your testid tests the same function as the AT tests,
then name it AT.
if you feel your test if different than the AT tests,
then you can name it something more appropriate.
the name should indicate the function you are testing.
back
