ID | Scenario | Steps | Expected Result | Actual Result | Status |
---|
1 | Snapshot versioning deployment and running services - failure | - Deploy Purchase app with Snapshot version
- Start Purchase HIstory Service
- Deploy updated version of the app, still with snapshot version
- Attempt to start the Purchase History Service
| The start from step 4 should fail with 409 status code | | |
2 | Snapshot versioning deployment and running services - success | - Deploy Purchase app with Snapshot version
- Start Purchase HIstory Service
- Deploy updated version of the app, still with snapshot version
- Stop the PurchaseHistory Service
- Attempt to start the Purchase History Service
| The start from Step 5 should succeed. The new code should be in effect | | |
3 | Deleting application with Snapshot versioning - failure | - Deploy Purchase app with Snapshot version
- Start Purchase HIstory Service
- Delete application
| The delete from Step 3 should fail | | |
4 | Deleting application with Snapshot versioning - success | - Deploy Purchase app with Snapshot version
- Start Purchase HIstory Service
- Stop Purchase History Service
- Delete application
| The delete from Step 4 should succeed | | |
5 | Concurrent non-snapshot services - success | - Deploy Purchase app with non-Snapshot version
- Start Purchase HIstory Service
- Deploy updated version of the app, still with non-snapshot version
- Attempt to start the Purchase History Service
- Route traffic to both services
| Both services should start, traffic should be routeable to both the instance of the running services | | |
6 | Setting routing configuration - failure | - Deploy Purchase app with non-snapshot version
- Configure 80% of traffic for Purchase History service
| The configuration call in step 2 should fail, because it is not 100% traffic | | |
7 | Setting routing configuration - failure | - Deploy Purchase app with non-snapshot version - v1
- Deploy Purchase app with non-snapshot version - v2
- Configure traffic to Purchase History Service v1-60%, v2 - 30%
| The configuration call in step 3 should fail, because it is not 100% traffic | | |
8 | Setting routing configuration - success | - Deploy Purchase app with non-snapshot version - v1
- Deploy Purchase app with non-snapshot version - v2
- Configure traffic to Purchase History Service v1-60%, v2 - 40%
| The configuration in step 3 should succeed | | |
9 | Setting routing traffic - success | - Deploy Purchase app with non-snapshot version - v1
- Deploy Purchase app with non-snapshot version - v2
- Configure traffic to Purchase History Service v1-60%, v2 - 40%
- Send 100 requests to the non versioned endpoint for service
| The traffic to v1 should be around 60% The traffic to v2 should be around 40% | | | | | | | | |
10 | Deleting app - versioned | - Deploy Purchase app with non-snapshot version - v1
- Deploy Purchase app with non-snapshot version - v2
- Delete app with version v1
- Start services with version v2
| Should be able to start the services and route traffic | | |
11 | | | | | Deleting app | - Deploy Purchase app with non-snapshot version - v1
- Deploy Purchase app with non-snapshot version - v2
- Use the non-versioned end-point to delete the app
| Should delete all versions of the app | | | | | | | | | |
12 | Namespace delete - failure | - Deploy Purchase app with non-snapshot version - v1
- Deploy Purchase app with non-snapshot version - v2
- Start services with v1 app
- Start services with v2 app
- Delete namespace in which the app is deployed
| The namespace delete should fail | | |
| | | | | |
| | | 13 | Namespace delete - success | - Deploy Purchase app with non-snapshot version - v1
- Deploy Purchase app with non-snapshot version - v2
- Start services with v1 app
- Start services with v2 app
- Stop services with v1
- Stop services with v2
- Delete namespace in which the app is deployed
| The namespace delete should succeed and on recreating the namespace the application should not exist | | |