Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
documentation
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
OCF
documentation
Commits
2b7f378d
Commit
2b7f378d
authored
6 months ago
by
Jorge Moratinos
Browse files
Options
Downloads
Plain Diff
Merge branch 'OCF-Doc17-add-vendor-extension-test-plan' into 'develop'
Minor fixes on test See merge request
!20
parents
b111d3f2
35fa5915
No related branches found
No related tags found
1 merge request
!20
Minor fixes on test
Pipeline
#10343
passed
6 months ago
Stage: deploy
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/testing/testplan/vendor_extensibility/README.md
+6
-6
6 additions, 6 deletions
doc/testing/testplan/vendor_extensibility/README.md
with
6 additions
and
6 deletions
doc/testing/testplan/vendor_extensibility/README.md
+
6
−
6
View file @
2b7f378d
...
...
@@ -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 V
endor
S
pecific
s parameters not publish
ed".
*
cause with message "Vendor
Ext feature active but vendorSpecifics not present
".
*
detail with message "
If and only if
VendorExt feature
is enabled, then v
endor
-s
pecific
fields should be defin
ed".
*
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 i
nactive at Supported Features but V
endor
S
pecific
s are present parameters publish
ed".
*
cause with message "Vendor
Ext feature inactive but vendorSpecifics present
".
*
detail with message "
If and only if
VendorExt feature i
s enabled, then v
endor
-s
pecific
fields should be defin
ed".
*
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"
...
...
This diff is collapsed.
Click to expand it.
Jorge Moratinos
@jorge.moratinossalcines
mentioned in commit
1af0bb51
·
6 months ago
mentioned in commit
1af0bb51
mentioned in commit 1af0bb51243fb56a016c0e396a8bf4062e350c19
Toggle commit list
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment