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: tests/service_automation/tests/features/is_api_features/dos_search_apim.feature
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Feature: API DoS Service Search APIM
9
9
10
10
11
11
12
-
Scenario Outline:I send a request to the dos-search Organization Endpoint by ODS Code via APIM with valid headers and query parameters
12
+
Scenario Outline:I send a request to the dos-search organization endpoint by ODS Code via APIM with valid headers and query parameters
13
13
When I request data from the APIM endpoint "Organization" with header "<params>" and query params "_revinclude=Endpoint:organization&identifier=odsOrganisationCode|M00081046"
14
14
Then I receive a status code "200" in response
15
15
And the response body contains a bundle
@@ -22,7 +22,7 @@ Feature: API DoS Service Search APIM
22
22
23
23
24
24
@manual
25
-
Scenario Outline:I send a request to the dos-search Organization Endpoint by ODS Code via APIM with invalid header and valid query parameters
25
+
Scenario Outline:I send a request to the dos-search organization endpoint by ODS Code via APIM with invalid header and valid query parameters
26
26
When I request data from the APIM endpoint "Organization" with header "<params>" and query params "_revinclude=Endpoint:organization&identifier=odsOrganisationCode|M00081046"
27
27
Then I receive a status code "400" in response
28
28
And the response body contains an "OperationOutcome" resource
@@ -37,15 +37,15 @@ Feature: API DoS Service Search APIM
37
37
38
38
39
39
40
-
Scenario:I send a request to the dos-search Organization Endpoint by ODS Code via APIM with valid query parameters
40
+
Scenario:I send a request to the dos-search organization endpoint by ODS Code via APIM with valid query parameters
41
41
When I request data from the APIM endpoint "Organization" with query params "_revinclude=Endpoint:organization&identifier=odsOrganisationCode|M00081046"
42
42
Then I receive a status code "200" in response
43
43
And the response body contains a bundle
44
44
And the bundle contains "1""Organization" resources
45
45
And the bundle contains "4""Endpoint" resources
46
46
47
47
48
-
Scenario Outline:I send a request to the dos-search Organization Endpoint via APIM with invalid ODS code
48
+
Scenario Outline:I send a request to the dos-search organization endpoint via APIM with invalid ODS code
49
49
When I request data from the APIM endpoint "Organization" with query params "<params>"
50
50
Then I receive a status code "400" in response
51
51
And the response body contains an "OperationOutcome" resource
@@ -62,7 +62,7 @@ Feature: API DoS Service Search APIM
Copy file name to clipboardExpand all lines: tests/service_automation/tests/features/is_api_features/dos_search_apim_security.feature
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -8,25 +8,25 @@ Feature: API DoS Service Search Is Secured
8
8
And I create a model in the repo from json file "Organisation/organisation-with-4-endpoints.json"
9
9
10
10
11
-
Scenario: I can access APIM for the 'ping' Endpoint and no access is required
11
+
Scenario: I can access APIM for the dos-search'ping' Endpoint and no access is required
12
12
When I request data from the APIM endpoint "_ping" with query params "" without authentication
13
13
Then I receive a status code "200" in response
14
14
15
15
16
-
Scenario: I can access APIM for the 'status' Endpoint and access is required
16
+
Scenario: I can access APIM for the dos-search 'status' Endpoint and access is required
17
17
When I request data from the APIM endpoint "_status" with query params "" with status token
18
18
Then I receive a status code "200" in response
19
19
20
20
21
-
Scenario: I search APIM for GP Endpoint by ODS Code with valid query parameters and a valid access token
21
+
Scenario: I search APIM for the dos-search organization endpoint by ODS Code with valid query parameters and a valid access token
22
22
When I request data from the APIM endpoint "Organization" with query params "_revinclude=Endpoint:organization&identifier=odsOrganisationCode|M00081046"
23
23
Then I receive a status code "200" in response
24
24
And the response body contains a bundle
25
25
And the bundle contains "1""Organization" resources
26
26
And the bundle contains "4""Endpoint" resources
27
27
28
28
29
-
Scenario: I cannot search APIM for GP Endpoint with invalid access token
29
+
Scenario: I cannot search APIM for the dos-search organization endpoint with invalid access token
30
30
When I request data from the APIM endpoint "Organization" with query params "_revinclude=Endpoint:organization&identifier=odsOrganisationCode|M00081046" with invalid token
31
31
Then I receive a status code "401" in response
32
32
And the response body contains an "OperationOutcome" resource
@@ -36,7 +36,7 @@ Feature: API DoS Service Search Is Secured
36
36
And the OperationOutcome contains an issue with diagnostics "Invalid or missing authentication token"
37
37
And the OperationOutcome contains an issue with details for INVALID_AUTH_CODING coding
38
38
39
-
Scenario: I cannot search APIM for GP Endpoint without authentication
39
+
Scenario: I cannot search APIM for the dos-search organization endpoint without authentication
40
40
When I request data from the APIM endpoint "Organization" with query params "_revinclude=Endpoint:organization&identifier=odsOrganisationCode|M00081046" without authentication
41
41
Then I receive a status code "401" in response
42
42
And the response body contains an "OperationOutcome" resource
Copy file name to clipboardExpand all lines: tests/service_automation/tests/features/is_api_features/dos_search_backend_gateway_errors.feature
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -8,13 +8,13 @@ Feature: API DoS Service Search Backend Gateway Errors
8
8
And I create a model in the repo from json file "Organisation/organisation-with-4-endpoints.json"
9
9
10
10
11
-
Scenario:I send a request to the dos-search Organization Endpoint by ODS Code with valid query parameters but missing mtls credentials and receive a connection reset error
11
+
Scenario:I send a request to the dos-search organization endpoint by ODS Code with valid query parameters but missing mtls credentials and receive a connection reset error
12
12
When I attempt to request data from the "dos-search" endpoint "Organization" without authentication but with valid query params "_revinclude=Endpoint:organization&identifier=odsOrganisationCode|M000081046"
13
13
Then I receive a connection reset error
14
14
15
15
16
16
17
-
Scenario:I send a request to the dos-search Organization Endpoint for a endpoint that does not exist and the api-gateway returns a 404 error
17
+
Scenario:I send a request to the dos-search organization endpoint for a endpoint that does not exist and the api-gateway returns a 404 error
18
18
When I request data from the "dos-search" endpoint "DoesNotExist" with query params "_revinclude=Endpoint:organization&identifier=odsOrganisationCode|M000081046"
19
19
Then I receive a status code "404" in response
20
20
And the response body contains an "OperationOutcome" resource
Copy file name to clipboardExpand all lines: tests/service_automation/tests/features/is_api_features/dos_search_backend_headers.feature
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Feature: API DoS Service Search Backend Gateway Headers
8
8
And I create a model in the repo from json file "Organisation/organisation-with-4-endpoints.json"
9
9
10
10
11
-
Scenario Outline:I send a request to the dos-search Organization Endpoint by ODS Code with valid query parameters and valid headers
11
+
Scenario Outline:I send a request to the dos-search organization endpoint by ODS Code with valid query parameters and valid headers
12
12
When I request data from the "dos-search" endpoint "Organization" with header "<params>" with query params "_revinclude=Endpoint:organization&identifier=odsOrganisationCode|M00081046"
13
13
Then I receive a status code "200" in response
14
14
And the response body contains a bundle
@@ -40,15 +40,15 @@ Feature: API DoS Service Search Backend Gateway Headers
Scenario:I send a request to the dos-search Organization Endpoint by ODS Code with valid query parameters and no headers
43
+
Scenario:I send a request to the dos-search organization endpoint by ODS Code with valid query parameters and no headers
44
44
When I request data from the "dos-search" endpoint "Organization" with query params "_revinclude=Endpoint:organization&identifier=odsOrganisationCode|M00081046"
45
45
Then I receive a status code "200" in response
46
46
And the response body contains a bundle
47
47
And the bundle contains "1""Organization" resources
48
48
And the bundle contains "4""Endpoint" resources
49
49
50
50
51
-
Scenario Outline:I send a request to the dos-search Organization Endpoint by ODS Code with valid query parameters and invalid headers
51
+
Scenario Outline:I send a request to the dos-search organization endpoint by ODS Code with valid query parameters and invalid headers
52
52
When I request data from the "dos-search" endpoint "Organization" with header "<params>" with query params "_revinclude=Endpoint:organization&identifier=odsOrganisationCode|M00081046"
53
53
Then I receive a status code "400" in response
54
54
And the response body contains an "OperationOutcome" resource
Copy file name to clipboardExpand all lines: tests/service_automation/tests/features/is_api_features/dos_search_backend_parameters.feature
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -7,15 +7,15 @@ Feature: API DoS Service Search Backend Request Parameters
7
7
And I have a organisation repo
8
8
And I create a model in the repo from json file "Organisation/organisation-with-4-endpoints.json"
9
9
10
-
Scenario:I send a request to the dos-search Organization Endpoint by ODS Code with for an ODS code that does not exist
10
+
Scenario:I send a request to the dos-search organization endpoint by ODS Code with for an ODS code that does not exist
11
11
When I request data from the "dos-search" endpoint "Organization" with query params "_revinclude=Endpoint:organization&identifier=odsOrganisationCode|X000081046"
12
12
Then I receive a status code "200" in response
13
13
And the response body contains a bundle
14
14
And the bundle contains "0""Organization" resources
15
15
And the bundle contains "0""Endpoint" resources
16
16
17
17
18
-
Scenario Outline:I send a request to the dos-search Organization Endpoint with invalid ODS code
18
+
Scenario Outline:I send a request to the dos-search organization endpoint with invalid ODS code
19
19
When I request data from the "dos-search" endpoint "Organization" with query params "<params>"
20
20
Then I receive a status code "400" in response
21
21
And the response body contains an "OperationOutcome" resource
@@ -32,7 +32,7 @@ Feature: API DoS Service Search Backend Request Parameters
Scenario Outline:I send a request to the dos-search Organization Endpoint with 1 missing parameter
67
+
Scenario Outline:I send a request to the dos-search organization endpoint with 1 missing parameter
68
68
When I request data from the "dos-search" endpoint "Organization" with query params "<params>"
69
69
Then I receive a status code "400" in response
70
70
And the response body contains an "OperationOutcome" resource
@@ -80,7 +80,7 @@ Feature: API DoS Service Search Backend Request Parameters
80
80
81
81
82
82
83
-
Scenario:I send a request to the dos-search Organization Endpoint with 2 missing parameters
83
+
Scenario:I send a request to the dos-search organization endpoint with 2 missing parameters
84
84
When I request data from the "dos-search" endpoint "Organization" with query params ""
85
85
Then I receive a status code "400" in response
86
86
And the response body contains an "OperationOutcome" resource
@@ -92,7 +92,7 @@ Feature: API DoS Service Search Backend Request Parameters
92
92
And the OperationOutcome contains an issue with details for INVALID_SEARCH_DATA coding
93
93
94
94
95
-
Scenario Outline:I send a request to the dos-search Organization Endpoint by ODS Code with unexpected query parameter
95
+
Scenario Outline:I send a request to the dos-search organization endpoint by ODS Code with unexpected query parameter
96
96
When I request data from the "dos-search" endpoint "Organization" with query params "_revinclude=Endpoint:organization&identifier=odsOrganisationCode|M00081046&<unexpected_param>=<unexpected_value>"
97
97
Then I receive a status code "400" in response
98
98
And the response body contains an "OperationOutcome" resource
@@ -109,6 +109,6 @@ Feature: API DoS Service Search Backend Request Parameters
109
109
110
110
@test
111
111
# New health check scenario for GET /_status
112
-
Scenario: I request a healthcheck of the GP Endpoint and receive a 200 response
112
+
Scenario: I request a healthcheck of the organization endpoint and receive a 200 response
113
113
When I request data from the "dos-search" endpoint "_status" with query params ""
0 commit comments