From 1a58bbe76eba50160565d02e63a5c3a4d5424d8e Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Mon, 8 Jun 2020 08:45:01 +0200 Subject: spec: Generalize directive to action requirements --- spec/spec/requirement-action-condition.yml | 40 ++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 spec/spec/requirement-action-condition.yml (limited to 'spec/spec/requirement-action-condition.yml') diff --git a/spec/spec/requirement-action-condition.yml b/spec/spec/requirement-action-condition.yml new file mode 100644 index 00000000..36fc34cb --- /dev/null +++ b/spec/spec/requirement-action-condition.yml @@ -0,0 +1,40 @@ +SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause +copyrights: +- Copyright (C) 2020 embedded brains GmbH (http://www.embedded-brains.de) +enabled-by: true +links: +- role: spec-member + uid: root +spec-description: null +spec-example: null +spec-info: + dict: + attributes: + name: + description: null + spec-type: requirement-action-name + states: + description: null + spec-type: requirement-action-state-list + test-epilogue: + description: | + If the value is present, then it shall be the test epilogue code. + The epilogue code is placed in the test condition preparation or + check before the state-specific code. The code may use a local + variable ``ctx`` which points to the test context, see + ${requirement-action-test-context:/spec-name}. + spec-type: optional-str + test-prologue: + description: | + If the value is present, then it shall be the test prologue code. + The prologue code is placed in the test condition preparation or + check after the state-specific code. The code may use a local + variable ``ctx`` which points to the test context, see + ${requirement-action-test-context:/spec-name}. + spec-type: optional-str + description: | + This set of attributes defines an action pre-condition or post-condition. + mandatory-attributes: all +spec-name: Action Requirement Condition +spec-type: requirement-action-condition +type: spec -- cgit v1.2.3