Test Scenarios
About
This document contains the test cases that will be used for automating using CDAP integration test suite. The first pass of test will be manual and these test cases will be automated in 3.6 timeframe.
Test Scenarios for application versioning
ID | Scenario | Steps | Expected Result | Actual Result | Status |
|---|---|---|---|---|---|
1 | Snapshot versioning deployment and running services - failure |
| 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 |
| 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 |
| The delete from Step 3 should fail |
| PASSED (09/21) PASSED (10/03) |
4 | Deleting application with Snapshot versioning - success |
| 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. PASSED (10/03) |
5 | Concurrent non-snapshot services - success |
| Both services should start, traffic should be routeable to both the instance of the running services |
| PASSED (09/21) PASSED (10/03)
|
6 | Setting routing configuration - failure |
| The configuration call in step 2 should fail, because it is not 100% traffic |
| PASSED (09/21) Faced an issue without deploying a versioned app.
Other issues while testing
PASSED (10/03)
|
7 | Setting routing configuration - failure |
| The configuration call in step 3 should fail, because it is not 100% traffic |
| PASSED (09/21) Faced in a issue without deploying versioned app Other issues while testing PASSED (10/03) |
8 | Setting routing configuration - success |
| The configuration in step 3 should succeed |
| PASSED (09/21) PASSED (10/03)
|
9 | Setting routing traffic - success |
| The traffic to v1 should be around 60% The traffic to v2 should be around 40% |
| PASSED (09/21) Percentages were Run 1: 63 - 37 Run 2: 62 - 38 Run 3: 66 - 34 Run 1: 72 - 28 |
10 | Deleting app - versioned |
| 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 (09/21) PASSED (10/03) |
11 | Deleting app |
| Should delete all versions of the app |
| FAILED (09/21) Non versioned delete endpoint doesn't exist PASSED (10/03) |
12 | Namespace delete - failure |
| The namespace delete should fail |
| PASSED (09/21) PASSED (10/03) |
13 | Namespace delete - success |
| The namespace delete should succeed and on recreating the namespace the application should not exist |
| FAILED (09/21) PASSED (10/03) |
14 | Deterministic routing - success |
| 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:
PASSED (10/03) |
15 | No route configuration |
| Requests should got to v1 or v2 based on default behavior configured. (Note: this test will fail now since this is not yet implemented ) |
| Not implemented PASSED (10/03) |
16 | Invalid route configuration |
| The request should fail with Bad Request |
| FAILED PASSED (10/03) |
Created in 2020 by Google Inc.