Issues #674
sCtl5 to be more precise related to "blocked" and "test/blocked"
Description
For steps 6,7,8 and 9,10,11 some statements to be added.
The existing steps apply for implementations where the LN instance hosting the controllable object is wired to electrical periphery. For other schemes, new test cases are to be created, stating which LN.Beh is "blocked", "test/blocked" respectively. For implementations where the LN instance hosting the controllable object is separated from the proxy LN instance which is wired to electrical periphery (ex. CSWI, XCBR), the AddCause "time-limit-over" may be issued since the proxy LN instance did not execute the control command.
The expected results for
- step6 add: The AddCause "blocked-by-mode" shall be issued.
- step7 ok
- step8 Since Tissue #1769 "The value of the test flag in the control command for Mod (Mod.Operate.test attribute) shall be ignored." the test could be amended to "... Mod control command with and without test flag set"
- step9 ok
- step10 add: The AddCause "blocked-by-mode" shall be issued.
- step11 same remark as for step8
Since sCtl28 was modified to no more include testing of "blocked" and "test/blocked", sCtl5 remains the only TP to test them. sCtl5 headline to be modified to state "blocked" and "test/blocked".
Files
Related issues