forked from automationExamples/pytest-api-example
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathBug Note Entry
More file actions
20 lines (17 loc) · 1.15 KB
/
Bug Note Entry
File metadata and controls
20 lines (17 loc) · 1.15 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Bug Note Entry-
1. Endpoint: /pets/{id}
- Expected Behavior: name property should be a string (e.g., "ranger")
- Actual Behavior: Schema incorrectly defines name as integer, causing validation failure
- Fix Applied: Updated schema in schemas.py to "type": "string" for name property
2. Endpoint: /pets/findByStatus
- Expected Behavior: Returns 200 and pets with matching status
- Actual Behavior: May return pets with incorrect/mixed statuses or missing fields
- Fix Applied: Parameterized test validates status and schema for each pet
3. Endpoint: /pets/{id}
- Expected Behavior: Returns 404 for invalid IDs with clear error message
- Actual Behavior: Sometimes returns 200 with empty JSON or inconsistent error text
- Fix Applied: Parameterized test asserts 404 and checks "not found" message
4. Endpoint: /store/order/{id} with PATCH
- Expected Behavior: Updates order status and returns 200 with message "Order and pet status updated successfully"
- Actual Behavior: May return 405 Method Not Allowed if PATCH isn’t implemented, or inconsistent message text
- Fix Applied: Wrote test to assert 200 and validate message/status; documented 405 as a bug if encountered