Filters
Positive / Negative
Priority
Tags
Functionality: API
| # | Test Case | +ve/-ve | Priority | Author | Vote | |
|---|---|---|---|---|---|---|
| 1. | Verify correct application state. This is optional and applies mainly to manual testing, or when a UI or another interface can be easily inspected | Positive | p1 |
Reviewed by Milin Patel
Reviewed on 2022-12-20 12:46:24
|
1
|
|
| 2. | Verify response headers. HTTP server headers have implications on both security and performance. | Positive | p1 |
Reviewed by Milin Patel
Reviewed on 2022-12-20 12:46:24
|
1
|
|
| 3. | Verify response payload. Check valid JSON body and correct field names, types, and values — including in error responses. | Positive | p1 |
Reviewed by Milin Patel
Reviewed on 2022-12-20 12:46:24
|
0
|
|
| 4. | Verify correct HTTP status code. For example, creating a resource should return 201 CREATED and unpermitted requests should return 403 FORBIDDEN, etc | Positive | p1 |
Reviewed by Milin Patel
Reviewed on 2022-12-20 12:46:24
|
0
|
|
| 5. | Verify that HTTP headers are as expected, including content-type, connection, cache-control, expires, access-control-allow-origin, keep-alive | Positive | p1 |
Reviewed by Milin Patel
Reviewed on 2022-12-20 12:46:24
|
0
|
|
| 6. | Verify that the API returns the appropriate error message or status code when an invalid request is made. | Negative | p1 |
Reviewed by Ramanuja Sagar Nukala
Reviewed on 2024-06-28 13:03:03
|
0
|
New Functionalities