From 35fa5915dc8e15bbebe3c6586e2d130aea6ac991 Mon Sep 17 00:00:00 2001 From: Jorge Moratinos Salcines Date: Fri, 29 Nov 2024 09:42:36 +0100 Subject: [PATCH] Minor fixes on test --- doc/testing/testplan/vendor_extensibility/README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/testing/testplan/vendor_extensibility/README.md b/doc/testing/testplan/vendor_extensibility/README.md index 53d58f2..bbc8f56 100644 --- a/doc/testing/testplan/vendor_extensibility/README.md +++ b/doc/testing/testplan/vendor_extensibility/README.md @@ -219,8 +219,8 @@ At this documentation you will have all information and related files and exampl 2. Error Response Body must accomplish with **ProblemDetails** data structure with: * status 400 * title with message "Bad Request" - * detail with message "VendorExt feature active at Supported Features but VendorSpecifics parameters not published". - * cause with message "VendorExt feature active but vendorSpecifics not present". + * detail with message "If and only if VendorExt feature is enabled, then vendor-specific fields should be defined". + * cause with message "Vendor extensibility misconfiguration". ## Test Case 5: Publish API with vendorExt inactive but with vendorSpecifics @@ -262,8 +262,8 @@ At this documentation you will have all information and related files and exampl 2. Error Response Body must accomplish with **ProblemDetails** data structure with: * status 400 * title with message "Bad Request" - * detail with message "VendorExt feature inactive at Supported Features but VendorSpecifics are present parameters published". - * cause with message "VendorExt feature inactive but vendorSpecifics present". + * detail with message "If and only if VendorExt feature is enabled, then vendor-specific fields should be defined". + * cause with message "Vendor extensibility misconfiguration". ## Test Case 6: Published API without vendor extensibility discover with VendSpecQueryParams enabled @@ -485,8 +485,8 @@ At this documentation you will have all information and related files and exampl 2. Error Response Body must accomplish with **ProblemDetails** data structure with: * status 400 * title with message "Bad Request" - * detail with message "supportedFeatures must be present in this request". - * cause with message "supportedFeatures missed". + * detail with message "supportedFeatures not present in request". + * cause with message "supportedFeatures not present". [service api description]: ../api_publish_service/service_api_description_post_example.json "Service API **Description** Request" -- GitLab