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
Copy file name to clipboardExpand all lines: src/openapi/TiMessengerTestTreiber.yaml
+24-1Lines changed: 24 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@ openapi: 3.0.3
2
2
info:
3
3
title: TiMessengerTestDriver
4
4
description: REST interface to automate the test of a TI-Messenger client implementation.
5
-
version: 0.9.2
5
+
version: 0.9.3
6
6
contact:
7
7
name: gematik GmbH
8
8
email: software-development@gematik.de
@@ -33,6 +33,8 @@ servers:
33
33
tags:
34
34
- name: info
35
35
description: This operation returns meta data about this interface and the status of available resources
36
+
- name: signalTestStart
37
+
description: This endpoint serves the possibility to clean system before test
36
38
- name: devices
37
39
description: Operations for device management
38
40
- name: account
@@ -83,6 +85,21 @@ paths:
83
85
default:
84
86
$ref: "#/components/responses/DefaultResponse"
85
87
88
+
post:
89
+
tags:
90
+
- signalTestStart
91
+
description: Implementation is optional! Testsuite sends a request to the org-admin endpoint of each involved homeserver (even if the org-admin is not named in the feature-file). There will be no claiming attempt before triggering this endpoint. After getting any response the testcase starts. This is an opportunity for the org-admin to clean user/rooms/FHIR-VZD etc. Even if errorcode returned the testsuite will start the test.
0 commit comments