diff options
| author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2020-08-14 08:57:04 +0200 |
|---|---|---|
| committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2020-08-19 11:29:34 +0200 |
| commit | 48d7a6858582560f763a51ed2ddb48fbeb079573 (patch) | |
| tree | 8540ba8ec2220a2afafaa2f74bd605a41b4659b9 /spec/spec/test-case.yml | |
| parent | b7e749b65fc22afd8eca5498a3931b81429146b8 (diff) | |
spec: Unify test attribute keys
Diffstat (limited to 'spec/spec/test-case.yml')
| -rw-r--r-- | spec/spec/test-case.yml | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/spec/spec/test-case.yml b/spec/spec/test-case.yml index b8862ae8..614bb98e 100644 --- a/spec/spec/test-case.yml +++ b/spec/spec/test-case.yml @@ -14,24 +14,24 @@ spec-example: null spec-info: dict: attributes: - actions: + test-actions: description: null spec-type: test-case-action-list - brief: + test-brief: description: | It shall be the test case brief description. spec-type: str - description: + test-description: description: | It shall be the test case description. spec-type: optional-str - epilogue: + test-epilogue: description: | If the value is present, then it shall be the test case epilogue code. The epilogue code is placed in the test case body after the test case actions. spec-type: optional-str - fixture: + test-fixture: description: | If the value is present, then it shall be a pointer to the test case fixture. The test case fixture pointer declaration may be provided @@ -40,27 +40,27 @@ spec-info: test-header: description: null spec-type: test-header - includes: + test-includes: description: | It shall be a list of header files included via ``#include <...>``. spec-type: list-str - local-includes: + test-local-includes: description: | It shall be a list of header files included via ``#include "..."``. spec-type: list-str - prologue: + test-prologue: description: | If the value is present, then it shall be the test case prologue code. The prologue code is placed in the test case body before the test case actions. A use case is the declaration of local variables used by the test case actions. spec-type: optional-str - support: + test-support: description: | If the value is present, then it shall be the test case support code. The support code is placed at file scope before the test case code. spec-type: optional-str - target: + test-target: description: | It shall be the path to the generated target test case source file. spec-type: str |