source: rtems-central/spec/spec/test-case.yml @ c970d63

Last change on this file since c970d63 was 48d7a68, checked in by Sebastian Huber <sebastian.huber@…>, on 08/14/20 at 06:57:04

spec: Unify test attribute keys

  • Property mode set to 100644
File size: 2.5 KB
Line 
1SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause
2copyrights:
3- Copyright (C) 2020 embedded brains GmbH (http://www.embedded-brains.de)
4enabled-by: true
5links:
6- role: spec-member
7  uid: root
8- role: spec-refinement
9  spec-key: type
10  spec-value: test-case
11  uid: root
12spec-description: null
13spec-example: null
14spec-info:
15  dict:
16    attributes:
17      test-actions:
18        description: null
19        spec-type: test-case-action-list
20      test-brief:
21        description: |
22          It shall be the test case brief description.
23        spec-type: str
24      test-description:
25        description: |
26          It shall be the test case description.
27        spec-type: optional-str
28      test-epilogue:
29        description: |
30          If the value is present, then it shall be the test case epilogue
31          code.  The epilogue code is placed in the test case body after the
32          test case actions.
33        spec-type: optional-str
34      test-fixture:
35        description: |
36          If the value is present, then it shall be a pointer to the test case
37          fixture.  The test case fixture pointer declaration may be provided
38          by the test case support code or via an included header file.
39        spec-type: optional-str
40      test-header:
41        description: null
42        spec-type: test-header
43      test-includes:
44        description: |
45          It shall be a list of header files included via ``#include <...>``.
46        spec-type: list-str
47      test-local-includes:
48        description: |
49          It shall be a list of header files included via ``#include "..."``.
50        spec-type: list-str
51      test-prologue:
52        description: |
53          If the value is present, then it shall be the test case prologue
54          code.  The prologue code is placed in the test case body before the
55          test case actions.  A use case is the declaration of local variables
56          used by the test case actions.
57        spec-type: optional-str
58      test-support:
59        description: |
60          If the value is present, then it shall be the test case support code.
61          The support code is placed at file scope before the test case code.
62        spec-type: optional-str
63      test-target:
64        description: |
65          It shall be the path to the generated target test case source file.
66        spec-type: str
67    description: |
68      This set of attributes specifies a test case.
69    mandatory-attributes: all
70spec-name: Test Case Item Type
71spec-type: test-case
72type: spec
Note: See TracBrowser for help on using the repository browser.