summaryrefslogtreecommitdiff
path: root/spec/spec/test-case.yml
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2020-06-04 09:56:51 +0200
committerSebastian Huber <sebastian.huber@embedded-brains.de>2020-06-08 08:59:20 +0200
commitf99047547159c41f363f96a36b4d134258ea52c8 (patch)
tree772c7cf8b897134aee8f06c23d6d50d3fcd664ea /spec/spec/test-case.yml
parentbb6010d0b4779206ae2ae30fbc5fa90ee4916458 (diff)
spec: Canonicalize descriptions
Diffstat (limited to 'spec/spec/test-case.yml')
-rw-r--r--spec/spec/test-case.yml26
1 files changed, 12 insertions, 14 deletions
diff --git a/spec/spec/test-case.yml b/spec/spec/test-case.yml
index b182b712..297d7108 100644
--- a/spec/spec/test-case.yml
+++ b/spec/spec/test-case.yml
@@ -27,16 +27,15 @@ spec-info:
spec-type: optional-str
epilogue:
description: |
- If the attribute 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.
+ 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:
description: |
- If the attribute value is present, then it shall be a pointer to the
- test case fixture. The test case fixture pointer declaration may be
- provided by the test case support code or via an included header
- file.
+ 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
+ by the test case support code or via an included header file.
spec-type: optional-str
includes:
description: |
@@ -51,16 +50,15 @@ spec-info:
spec-type: test-name
prologue:
description: |
- If the attribute 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.
+ 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:
description: |
- If the attribute 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.
+ 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:
description: |