Commit 8101b086 authored by Akshat  Joshi's avatar Akshat Joshi
Browse files

Modify IT

parent 3a9c1233
Pipeline #112836 failed with stages
in 33 seconds
......@@ -30,13 +30,14 @@ Feature: To verify functionality of PUT schema Service
| "/input_payloads/postInPrivateScope_positiveScenario.json" | "200" | "200" | "/output_payloads/UpdatedResolvedSchema.json" | "/input_payloads/putUpdatedSchema_positiveScenario.json" |
@SchemaServiceAzure
Scenario Outline: Verify that Schema Service's PUT API throws error if put request tries to create new record in obsolete status
Scenario Outline: Verify that Schema Service's PUT API throws error if put request tries to create new record without development status
Given I hit schema service PUT API with <InputPayload> and mark schema as <status> for next major version
Then service should respond back with error <ReponseStatusCode> and <ResponseMessage>
Examples:
| InputPayload | ReponseStatusCode | ResponseMessage | status |
| "/input_payloads/postInPrivateScope_positiveScenario.json" | "400" | "/output_payloads/SchemaPut_InvalidStatusMessage.json" | "OBSOLETE" |
| "/input_payloads/postInPrivateScope_positiveScenario.json" | "400" | "/output_payloads/SchemaPut_InvalidStatusMessage.json" | "PUBLISHED" |
@SchemaServiceAzure
Scenario Outline: Verify that Schema Service's PUT API throws error if modification in schemaInfo is requested
......
......@@ -37,12 +37,12 @@ Feature: To verify functionality of PUT schema Service
Then service should respond back with error <ReponseStatusCode> and <ResponseMessage>
Examples:
| InputPayload | ReponseStatusCode | ResponseMessage | status |
| "/input_payloads/postInPrivateScope_positiveScenario.json" | "400" | "/output_payloads/SchemaPut_InvalidStatusMessage.json" | "OBSOLETE" |
| "/input_payloads/postInPrivateScope_positiveScenario.json" | "400" | "/output_payloads/SchemaPut_InvalidStatusMessage.json" | "PUBLISHED" |
| InputPayload | ReponseStatusCode | ResponseMessage | status |
| "/input_payloads/postInPrivateScope_positiveScenario.json" | "200" | "/output_payloads/SchemaPost_PrivateScope_SuccessfulCreation.json" | "OBSOLETE" |
| "/input_payloads/postInPrivateScope_positiveScenario.json" | "200" | "/output_payloads/SchemaPost_PrivateScope_SuccessfulCreation.json" | "PUBLISHED" |
@SchemaService
Scenario Outline: Verify that System schema PUT API throws error if modification in schemaInfo is requested
Scenario Outline: Verify that System schema PUT API throws e rror if modification in schemaInfo is requested
Given I hit system schema PUT API with <InputPayload> with different entityType
Then put schema service should respond back with <ReponseStatusCodeForPUT>
Given I set request headers for "TENANT1"
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment