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 | | PASSED (09/21) PASSED (10/03) |
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 | | PASSED (09/21) PASSED (10/03) |
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 | | PASSED (09/21) PASSED (10/03) |
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 and PurchaseHistory app should not appear in the listing end point | | FAILED (09/21) There is another app with artifact version is created. Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration. PASSED (10/03) |
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 | | PASSED (09/21) |
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 | | PASSED. Faced an issue without deploying a versioned app.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Other issues while testing
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
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 | | PASSED. Faced in a issue without deploying versioned app
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Other issues while testing
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
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 | | PASSED |
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% | | PASSED. Percentages were Run 1: 63 - 37 Run 2: 62 - 38 Run 3: 66 - 34 |
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 (What should be the expected behavior of routing traffic after one version is deleted?) Sree: Delete should fail if there is a route for the version to be deleted. | | PASSED |
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 | | FAILED Non versioned delete endpoint doesn't exist |
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 | | PASSED |
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 | | FAILED
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
14 | Deterministic routing - 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 requests to v1 service
- Send requests to v2 service
| v1 requests should go to v1 service, and v2 requests should go to v2 service | | Cannot verify. The endpoints for deterministic routing is not present As a workaround: - Set the routing percetage to 100, 0 to old vs new and send requests to non-versioned endpoint Ex:
v3/namespaces/default/apps/WordCount/services/RetrieveCounts/methods/greeting And flip the percentage to 0, 100 to redirect all traffic to new endpoint
|
15 | No route configuration | - Deploy Purchase app with non-snapshot version - v1
- Deploy Purchase app with non-snapshot version - v2
- Send request without setting route config
| Requests should got to v1 or v2 based on default behavior configured. (Note: this test will fail now since this is not yet implemented
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
) | | Not implemented |
16 | Invalid route configuration | - Deploy Purchase app with non-snapshot version - v1
- Deploy Purchase app with non-snapshot version - v2
- Set route config for service with versions (v1, v2, v3) where v3 is non-existing version
| The request should fail with Bad Request | | FAILED
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|