You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update reference docs (conceptual and API usage) to match latest APIs (#94)
* Update data document to match current fields
* test sessions -> test results
* Update metadata document to match current fields
* Update 'using' document to reflect current APIs
* Update 'condition_type' parameter name.
---------
Co-authored-by: Joel Dixon <joel.dixon@emerson.com>
An **Operator** represents a person who performs tests or operates test equipment. This captures the human element in your test process.
9
11
10
12
**Fields:**
11
13
-`id` (string) - The id of the operator
12
14
-`name` (string) - The name of the operator
13
15
-`role` (string) - The role of the operator (e.g., "Test Engineer", "Lab Technician")
14
16
-`link` (string) - URI to resource describing the operator
15
-
-`extensions` (dict) - Custom key-value pairs for additional metadata
17
+
-`extension` (dict) - Custom key-value pairs for additional metadata
16
18
-`schema_id` (string) - ID of the schema for extension validation
17
19
18
20
**Real-world examples**:
@@ -27,10 +29,10 @@ A **Test Station** represents a physical location or setup where testing is perf
27
29
28
30
**Fields:**
29
31
-`id` (string) - The id of the test station
30
-
-`test_station_name` (string) - The name of the test station
32
+
-`name` (string) - The name of the test station
31
33
-`asset_identifier` (string) - For tracking and inventory purposes
32
34
-`link` (string) - URI to resource describing the test station
33
-
-`extensions` (dict) - Custom key-value pairs for additional metadata
35
+
-`extension` (dict) - Custom key-value pairs for additional metadata
34
36
-`schema_id` (string) - ID of the schema for extension validation
35
37
36
38
**Real-world examples**:
@@ -51,7 +53,7 @@ A **UUT** represents a product definition or model being tested. This is the "wh
51
53
-`manufacturers` (list of strings) - List of manufacturers of the UUT
52
54
-`part_number` (string) - The part number of the UUT
53
55
-`link` (string) - URI to resource describing the UUT
54
-
-`extensions` (dict) - Custom key-value pairs for additional metadata
56
+
-`extension` (dict) - Custom key-value pairs for additional metadata
55
57
-`schema_id` (string) - ID of the schema for extension validation
56
58
57
59
**Real-world examples**:
@@ -73,7 +75,7 @@ A **UUT Instance** represents an individual physical device with a unique serial
73
75
-`firmware_version` (string) - Version of the firmware on the UUT instance
74
76
-`hardware_version` (string) - Hardware version of the UUT instance
75
77
-`link` (string) - URI to resource describing the UUT instance
76
-
-`extensions` (dict) - Custom key-value pairs for additional metadata
78
+
-`extension` (dict) - Custom key-value pairs for additional metadata
77
79
-`schema_id` (string) - ID of the schema for extension validation
78
80
79
81
**Real-world examples**:
@@ -95,7 +97,7 @@ A **Hardware Item** represents test equipment, instruments, or tools used during
95
97
-`asset_identifier` (string) - For tracking and inventory purposes
96
98
-`calibration_due_date` (string) - When calibration expires
97
99
-`link` (string) - URI to resource describing the hardware item
98
-
-`extensions` (dict) - Custom key-value pairs for additional metadata
100
+
-`extension` (dict) - Custom key-value pairs for additional metadata
99
101
-`schema_id` (string) - ID of the schema for extension validation
100
102
101
103
**Real-world examples**:
@@ -114,7 +116,7 @@ A **Software Item** represents software tools, environments, or versions used du
114
116
-`product` (string) - The software product name (letters, numbers, spaces, hyphens, underscores, parentheses, periods; must begin and end with letter or number)
115
117
-`version` (string) - The version of the software item
116
118
-`link` (string) - URI to resource describing the software item
117
-
-`extensions` (dict) - Custom key-value pairs for additional metadata
119
+
-`extension` (dict) - Custom key-value pairs for additional metadata
118
120
-`schema_id` (string) - ID of the schema for extension validation
119
121
120
122
**Real-world examples**:
@@ -132,9 +134,9 @@ A **Test Description** represents a defined test procedure or specification for
132
134
**Fields:**
133
135
-`id` (string) - The id of the test description
134
136
-`uut_id` (string) - The ID of the UUT this test is designed for
135
-
-`test_description_name` (string) - Name of the test description
137
+
-`name` (string) - Name of the test description
136
138
-`link` (string) - URI to resource describing the test description
137
-
-`extensions` (dict) - Custom key-value pairs for additional metadata
139
+
-`extension` (dict) - Custom key-value pairs for additional metadata
138
140
-`schema_id` (string) - ID of the schema for extension validation
139
141
140
142
**Real-world examples**:
@@ -148,10 +150,10 @@ A **Test** represents an individual test procedure or method. This is more granu
148
150
149
151
**Fields:**
150
152
-`id` (string) - The id of the test
151
-
-`test_name` (string) - Name of the test
153
+
-`name` (string) - Name of the test
152
154
-`description` (string) - Explanation of what the test does
153
155
-`link` (string) - URI to resource describing the test
154
-
-`extensions` (dict) - Custom key-value pairs for additional metadata
156
+
-`extension` (dict) - Custom key-value pairs for additional metadata
155
157
-`schema_id` (string) - ID of the schema for extension validation
156
158
157
159
**Real-world examples**:
@@ -173,7 +175,7 @@ A **Test Adapter** represents a test fixture, mechanical setup, or interface use
173
175
-`asset_identifier` (string) - For tracking and inventory purposes
174
176
-`calibration_due_date` (string) - When calibration expires
175
177
-`link` (string) - URI to resource describing the test adapter
176
-
-`extensions` (dict) - Custom key-value pairs for additional metadata
178
+
-`extension` (dict) - Custom key-value pairs for additional metadata
177
179
-`schema_id` (string) - ID of the schema for extension validation
178
180
179
181
**Real-world examples**:
@@ -269,7 +271,7 @@ hardware_item = HardwareItem(
269
271
manufacturer="NI",
270
272
model="PXIe-5171",
271
273
serial_number="SCOPE001",
272
-
extensions={
274
+
extension={
273
275
"bandwidth": "1 GHz",
274
276
"manufacture_date": "2024-03-15",
275
277
"calibration_certificate": "CAL-2024-001234",
@@ -349,7 +351,7 @@ hardware_item = HardwareItem(
349
351
model="PXIe-5171",
350
352
serial_number="SCOPE001",
351
353
schema_id=schema_id, # Links to registered schema
352
-
extensions={
354
+
extension={
353
355
"bandwidth": "1 GHz", # Required by schema
354
356
"manufacture_date": "2024-03-15", # Required by schema
355
357
"asset_tag": "SCOPE-789"# Optional field
@@ -390,7 +392,7 @@ hardware_item = HardwareItem(
390
392
manufacturer="NI",
391
393
model="PXIe-4081",
392
394
# schema_id automatically inherited from test_result
0 commit comments