TestMace
Search…
0.0.1-beta.24
Node Types
Working with the project
Settings
Other features
Assertion
Assertion nodes are used in writing tests. Each Assertion node consists of several assertions - statements that allow you to test certain assumptions. When you run an Assertion node, you run all assertions. If any test raises an error, the entire Assertion node run is unsuccessful.
An Assertion node can only be created as a child of a RequestStep node. At the same time, a RequestStep node can have only one Assertion node as a child.
There are two ways to create an Assertion node. First, choose Add node -> Assertion from a RequestStep node context menu. Second, click + CREATE NEW ASSERTION NODE on the Assertion tab of the RequestStep node response area.
This is how an Assertion node looks like in the project tree:
If an Assertion node was run successfully, its icon in the project tree looks like that:
If an Assertion node was run unsuccessfully, its icon in the project tree changes to this:
There are several actions you can do with this node type:
- Remove node. Use it to delete the node.
- Run. Run the node.
- Show in explorer. Open the folder with the node in the file manager.
The Assertion node tab has the following interface:
In the screenshot you can see the following parts of the interface:
- 1.The control panel
- 2.The settings panel for the chosen assertion
- 3.The list of all assertions
You can see the following buttons on the control panel:
- RUN - runs all assertions in the list.
- FIX ERRORS - fixes assertions errors if possible The button is available if there are some errors in the assertions. The error fixing algorithms are described for each assertion type separately.
- DISABLE ERRORS - disables the failed assertions. They won't be included in further runs. The button is available if there are some errors in the assertions.
- + ADD ASSERTION - adds an assertion to the list.
The assertions list is right under the control panel. Each element of the list has the looks like this:
In the screenshot you can see the following parts of the interface:
- 1.Status highlighting. Its status is gray, if the assertion hasn't been run yet, red - if the run failed, green - if it was successful.
- 2.Drag-and-drop point.
- 3.The assertion type icon.
- 4.The assertion text representation.
- 5.Show/hide error details button.
- 6.Delete the assertion.
- 7.Disable the assertion. It won't be included in the further runs.
- 8.Run the assertion.
- 9.Fix the assertion.
Note that the controls 6, 7, 8, and 9 appear when you hover the mouse over the assertion.
The interface of the settings panel depends on the chosen assertion type. We'll discuss all of them in the next sections.
Each Assertion has a
Name field to specify what is being tested. If the field is empty, a default description is set according to the assertion properties.Assertion Template
Starting from the 1.0.0 version, an Assertion node may be created without any connection to a RequestStep node, as any other node in the project. It can be used for checking results of multiple requests or as a template where a set of standard assertions is defined.
As compared to an Assertion which is related to a RequestStep node and inherits its context (variables, dynamic variables, response), an assertion template inherits the context of the node which refers to this template while running. The context is saved to the
$host built-in variable and is initialized only after running.Running an assertion template separately doesn't make any sense, since there is no context available and all assertions are going to be failed. For this reason, we eliminate this possibility in TestMace, and nodes of this type will be skipped while running scenarios.
For debugging purposes, in the template interface you'll see the name of the node that was run last and sent its context to the template. In this case, values highlighting and autocomplete for every expression containing the
$host variable will be available.To learn more about using independent Assertion nodes as templates and to see some examples of that, please refer to the Link Assertion section.
File Representation
An Assertion node is stored in the <nodename>.yml file, where <nodename> is the Assertion node name. The file has the following format:
1
{
2
"type": "object",
3
"properties": {
4
"type": {
5
"description": "Type of Assertion node",
6
"const": "Assertion",
7
"type": "string"
8
},
9
"assertions": {
10
"description": "List of assertions",
11
"type": "array",
12
"items": {
13
"$ref": "#/definitions/AbstractAssertion"
14
},
15
"default": []
16
},
17
"children": {
18
"description": "List of children names",
19
"type": "array",
20
"items": {
21
"type": "string"
22
},
23
"default": []
24
},
25
"variables": {
26
"$ref": "#/definitions/NodeVariables",
27
"description": "Node variables dictionary"
28
},
29
"name": {
30
"description": "Node name",
31
"type": "string"
32
}
33
},
34
"required": [
35
"assertions",
36
"children",
37
"name",
38
"type",
39
"variables"
40
],
41
"definitions": {
42
"AbstractAssertion": {
43
"oneOf": [
44
{
45
"$ref": "#/definitions/CompareAssertion"
46
},
47
{
48
"$ref": "#/definitions/ContainsAssertion"
49
},
50
{
51
"$ref": "#/definitions/XPathAssertion"
52
},
53
{
54
"$ref": "#/definitions/ScriptAssertion"
55
}
56
]
57
},
58
"CompareAssertion": {
59
"type": "object",
60
"properties": {
61
"type": {
62
"description": "Type of Compare assertion",
63
"const": "compare",
64
"type": "string"
65
},
66
"actualValue": {
67
"description": "Actual value",
68
"type": "string",
69
"default": "${$response.body}"
70
},
71
"operator": {
72
"$ref": "#/definitions/CompareOperator",
73
"description": "Operator",
74
"default": "equal"
75
},
76
"expectedValue": {
77
"description": "Expected value",
78
"type": "string"
79
},
80
"disabled": {
81
"type": "boolean",
82
"default": false
83
}
84
},
85
"required": [
86
"actualValue",
87
"disabled",
88
"expectedValue",
89
"operator",
90
"type"
91
]
92
},
93
"CompareOperator": {
94
"enum": [
95
"equal",
96
"greater",
97
"greater or equal",
98
"less",
99
"less or equal",
100
"not equal"
101
],
102
"type": "string"
103
},
104
"ContainsAssertion": {
105
"type": "object",
106
"properties": {
107
"type": {
108
"description": "Type of Contains assertion",
109
"const": "contains",
110
"type": "string"
111
},
112
"text": {
113
"description": "Text to be searched",
114
"type": "string",
115
"default": "${$response.body}"
116
},
117
"value": {
118
"description": "Value for search in text",
119
"type": "string"
120
},
121
"disabled": {
122
"type": "boolean",
123
"default": false
124
}
125
},
126
"required": [
127
"disabled",
128
"text",
129
"type",
130
"value"
131
]
132
},
133
"XPathAssertion": {
134
"type": "object",
135
"properties": {
136
"type": {
137
"description": "Type of Xpath assertion",
138
"const": "xpath",
139
"type": "string"
140
},
141
"text": {
142
"description": "Text to be searched",
143
"type": "string",
144
"default": "${$response.body}"
145
},
146
"path": {
147
"description": "XPath selector",
148
"type": "string"
149
},
150
"expectedValue": {
151
"description": "Expected value",
152
"type": "string"
153
},
154
"disabled": {
155
"type": "boolean",
156
"default": false
157
}
158
},
159
"required": [
160
"disabled",
161
"expectedValue",
162
"path",
163
"text",
164
"type"
165
]
166
},
167
"ScriptAssertion": {
168
"type": "object",
169
"properties": {
170
"type": {
171
"description": "Type of Script assertion",
172
"const": "script",
173
"type": "string"
174
},
175
"script": {
176
"description": "Assertion script",
177
"type": "string",
178
"default": "`function test(assertion, variables) {\n // It should return true if test is passed\n // return true;\n}`"
179
},
180
"disabled": {
181
"type": "boolean",
182
"default": false
183
}
184
},
185
"required": [
186
"disabled",
187
"script",
188
"type"
189
]
190
},
191
"NodeVariables": {
192
"type": "object",
193
"additionalProperties": {
194
"type": "string"
195
}
196
}
197
},
198
"$schema": "http://json-schema.org/draft-07/schema#"
199
}
Copied!
Last modified 1yr ago
Copy link