[email protected]
TESTING : our job
- Test every requirement listed in the DSS.
- Get 100% TCA (cover all if-then branches).
- Sign off all FPTEST SCRs.
what is a DSS Requirement?
- Logic
- Variables
PROCESS:
- Choose a BASELINE.
Have the BASELINE SUT conveniently available.
Have the BASELINE DSS conveniently available.
- Define DSS Variables:
- Compare Code and DSS to verify all Variables are implemented.
- Update CT and BD Files:
CT: DSS name -> BD name
BD: BD name -> Bitwise Representation
- Create or Alter a TDF test file from BASELINE DSS Logic.
- Produce SSI from TDF utilizing DAP with appropriate setenv reference.
- DWS Debug of TDF, generate Problem Report (if indicated)
- TDI Test Design Inspection
- Schedule & Closure of Insections at HISO, via E-Mail tool
- File types to be put in ACM:
- TDF
- INC
- CT
- BD
- RES
- RPT
- INS
- Inspect TRACE for accuracy
- Return to STEP(2) to complete the Functional Area
eg, EPD_OQ0xxx (all ENG -- Oil Quantity TDFs)
- TCA Coverage
- Generate TFL file for Functional Area
- Coverage per Functional Area
eg, sculc B36SWIT302 "OIL_QUANTITY" ....
- 90% Coverage sufficient
- TEI Test Execution Inspection
- Schedule & Closure of Insections at HISO, via E-Mail tool
- File types to be put in ACM:
-
Return to STEP(2) to complete the NEXT Functional Area
eg, EPD_OP0xxx (ENG -- Oil Pressure)
- SCR Rework. Return to STEP(1) to complete any SCRs
not included in the Initial Development Baseline.
- RFS
- Schedule an ITRR
- File types to be put in ACM:
NOTES:
SCR TYPES:
- INITIAL DEVELOPMENT
- SCR Rework
- RFS Artifacts
- RFS Fixes
Types of Development:
- Update -- DSS Change and Code Change
- Rerun -- No DSS Change, but the Code Changed
- Reuse -- No DSS Change, and no Code Change
back
