Please enable JavaScript.
Coggle requires JavaScript to display documents.
API versioning - Coggle Diagram
-
API versioning
Validate the gateway call by creating a REST API with the correct default version - TC01
Validate the gateway call by creating a REST API with the incorrect default version - TC02
-
-
-
Validate the gateway call after creating a new version of an existing API with a single environment - TC05
-
Validate the gateway call after creating a new version of an existing API with multiple environments - TC06
-
Validate the gateway call by adding a new environment for the cloning new version of the existing API
Use already created API with multiple environments (Env1, Env2)
-
-
-
Validate the gateway call after creating a new version of an existing API with multiple pools
(API level - pool1, Resource level - pool2, Operational level - pool3) - TC08
-
Validate the gateway call by adding a new pool to a new version of the existing API with multiple pools
(API level - pool1, Resource level - pool2, Operational level - pool3)
Use the already created API with multiple pools at different levels
(API level - pool1, Resource level -> resource1 -> pool2, Operation level -> POST -> pool3)
-
Validate the gateway call by deleting a pool from a new version of the existing API
(API level - pool1, Resource level - pool2, Operational level - pool3)
Use the already created API with multiple pools at different levels
(API level - pool1, Resource level -> resource1 -> pool2, Operation level -> POST -> pool3)
-
Validate the gateway call after creating a new version of an existing API with a single scope - TC09
-
Validate the gateway call after creating a new version of an existing API with multiple scopes
(API level - scope1, Resource level - scope2, Operational level - scope3) - TC10
Use the already created API with multiple pools at different levels
(API level - scope1, Resource level -> resource1 -> scope2, Operation level -> POST -> scope3)
-
-
-
Validate the gateway call by creating a new version of the API with an API throttler
(throttler1 -> 5 requests per 1 min)
Use the already created API, which has throttler1 at the API level
-
Validate the gateway call by creating a new version of the API with multiple API throttlers
(API level -> throttler1 -> 10 requests per 1 min, Resource level -> 6 requests per 1 min, Method level -> 4 request per 1 min)
Use the already created API, which has throttler1 at the API level, throttler2 at the resource level (resource1), and throttler3 at the operational level(resource1->POST)
-
Validate the gateway call by adding an API throttle to a new version of the API
(throttler1 -> 5 requests per 1 min)
Use the already created API, which has throttler1 at the API level
-
Validate the gateway call by deleting an API throttle from a new version of the API
(throttler1 -> 5 requests per 1 min)
Use the already created API, which has throttler1 at the API level
-
-
-
-
-
Validate the gateway call by removing the existing resource path from the new version of the existing API
-
-
Validate gateway call when the API status of a newly created version is changed from Testing to Alpha
Validate gateway call when the API status of a newly created version is changed from Testing to Beta
Validate gateway call when the API status of a newly created version is changed from Testing to Production
Validate gateway call when the API status of a newly created version is changed from Testing to Deprecated
Validate gateway call when the API status of a newly created version is changed from Testing to Retired
-
-