Attendees: Gerald Chan, Ric Dokken, Carey Garrenton, Greg Maston, Jim O'Reilly, Ernie Wahl Line and clause numbers if any are with regard to STIL.4 syntax document D02 dated November 09, 2015. ================================================================================ DISCUSSION: Q. What problem(s) are we trying to solve with execResult ? A. require a standard reserved keyword that: - represents values that cannot be clearly classified as pass or fail - provides read-only access by user in STIL.4 - remains flexible for STIL.5 where it may be set by a tool or user on a per test-type basis. Questions and answers regarding semantics: Q. What causes execResult to be set (reset) ? A. set by FlowNode TestExec via ATE operating system, not the user (at least not in STIL.4) Q. When a FlowNode executes a flow that contains multiple tests, what value will its execResult take on ? A. last executed test Q. Scope: from where may it be referenced ? A. Post-TestExec in FlowNode, i.e., PostActions and port-actions Q. What value will execResult return if referenced before it is set ? A. Can't be referenced before it is set Q. Will it hide or conflict with a variable named execResult ? A. No because it is a standard reserved keyword Q. Does ExecResult still have the rough-grained/fine-grained relationship with FailMode ? A. ExecResult and FailMode have no relationship in STIL.4 Q. Are the semantics currently described under TestBase applicable ? A. No ================================================================================ ACTION ITEMS: Ernie: with regard to TestBase, remove execResult, change variable name "TestNumber" to "testNumber" and "FailMode" to "failMode" (in red). Globally change "failed" to "failMode". Jim: add TestNumber and execResult to "Table 1—Additional Global STIL.4 Reserved Words" Carey: add port using failMode to Figure 65 example, submit via email Ric: globally change CurrentExec.execResult -> execResult ================================================================================