diff options
| author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2021-02-04 07:48:19 +0100 |
|---|---|---|
| committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2021-02-04 14:23:14 +0100 |
| commit | 5591cc2fd4619784ec64bb0634eca7a43d99bfbc (patch) | |
| tree | d91adbac86dca07f67e9312f6211ed107ac9b37c /spec/spec/test-case.yml | |
| parent | e45117ddac66270b170f2e6caa3def6d2425eda6 (diff) | |
validation: Add context and fixture to test case
Diffstat (limited to 'spec/spec/test-case.yml')
| -rw-r--r-- | spec/spec/test-case.yml | 24 |
1 files changed, 18 insertions, 6 deletions
diff --git a/spec/spec/test-case.yml b/spec/spec/test-case.yml index 614bb98e..0a03d25e 100644 --- a/spec/spec/test-case.yml +++ b/spec/spec/test-case.yml @@ -21,6 +21,15 @@ spec-info: description: | It shall be the test case brief description. spec-type: str + test-context: + description: null + spec-type: test-context-list + test-context-support: + description: | + If the value is present, then it shall be the test context support + code. The context support code is placed at file scope before the + test context definition. + spec-type: optional-str test-description: description: | It shall be the test case description. @@ -31,12 +40,6 @@ spec-info: code. The epilogue code is placed in the test case body after the test case actions. spec-type: optional-str - 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 - by the test case support code or via an included header file. - spec-type: optional-str test-header: description: null spec-type: test-header @@ -55,6 +58,12 @@ spec-info: test case actions. A use case is the declaration of local variables used by the test case actions. spec-type: optional-str + test-setup: + description: null + spec-type: test-support-method + test-stop: + description: null + spec-type: test-support-method test-support: description: | If the value is present, then it shall be the test case support code. @@ -64,6 +73,9 @@ spec-info: description: | It shall be the path to the generated target test case source file. spec-type: str + test-teardown: + description: null + spec-type: test-support-method description: | This set of attributes specifies a test case. mandatory-attributes: all |