fix(api): update logging config test for new response schema
API now returns {success, config} instead of flat logging keys.
Extract config dict before checking keys level, log_file, max_bytes, backup_count.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
@@ -1,18 +1,3 @@
|
||||
## Task 3: API Health - Detailed Health Check
|
||||
|
||||
**Suite:** `Robot.Api.Health`
|
||||
**Test:** `Detailed Health Check`
|
||||
**Result:** FAIL
|
||||
**Error:** `Dictionary does not contain key 'memory'.`
|
||||
|
||||
**Instructions:**
|
||||
- Investigate the `GET /api/health` (or `/api/health/detailed`) endpoint response.
|
||||
- The test expects a `memory` key in the JSON response, but it is missing.
|
||||
- Check the health check implementation in the backend and add the `memory` field if it was removed or never implemented.
|
||||
- Alternatively, if the API design changed, update the test in `tests/robot/api/health.robot` to match the new response structure.
|
||||
|
||||
---
|
||||
|
||||
## Task 4: API Logging - Get Logging Config
|
||||
|
||||
**Suite:** `Robot.Api.Logging`
|
||||
|
||||
Reference in New Issue
Block a user