Commit 3a9c1233 authored by Akshat  Joshi's avatar Akshat Joshi
Browse files

new ITs for service

parent e9ee9a1c
Pipeline #112684 failed with stages
in 53 seconds
......@@ -30,14 +30,13 @@ 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 without development status
  • @aj I hope we are not modifying the existing behavior of the PUT endpoint for private schemas.

    Please note that there are two PUT endpoints:

    • /schema : Does not support schema creation for status other than DEVELOPMENT
    • /schemas/system: Since we have not created a dedicated POST endpoint for system-schema, we are enabling schema creation in any status.

    image

    Edited by Abhishek Kumar (SLB)
  • Author Maintainer

    Like it should not create schema in Obsolete mode

  • It must throw error for both OBSOLETE OR PUBLISHED

  • The problem here is that we are reusing the underlying services which was originally designed for PUT endpoint. With creation of System endpoint we should have its own service method rather putting lots of if-else logic.

  • Author Maintainer

    Ok

Please register or sign in to reply
Scenario Outline: Verify that Schema Service's PUT API throws error if put request tries to create new record in obsolete 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
......
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