Fix backend API test errors

[frankbria]

The following API tests are failing with the following information:

FAILED tests/api/test_api_discovery_progress.py::TestDiscoveryProgressEndpoint::test_get_discovery_progress_returns_null_when_discovery_not_started - assert 403 == 200
FAILED tests/api/test_api_discovery_progress.py::TestDiscoveryProgressEndpoint::test_get_discovery_progress_returns_progress_when_discovering - assert 403 == 200
FAILED tests/api/test_api_discovery_progress.py::TestDiscoveryProgressEndpoint::test_get_discovery_progress_returns_100_percent_when_completed - assert 403 == 200
FAILED tests/api/test_api_discovery_progress.py::TestDiscoveryProgressEndpoint::test_get_discovery_progress_matches_project_phase - assert 403 == 200
FAILED tests/api/test_api_discovery_progress.py::TestDiscoveryProgressEndpoint::test_get_discovery_progress_excludes_answers_field - assert 403 == 200
FAILED tests/api/test_api_issues.py::TestIssuesEndpointBasics::test_issues_endpoint_returns_200 - assert 403 == 200
FAILED tests/api/test_api_issues.py::TestIssuesResponseStructure::test_issues_response_has_required_fields - AssertionError: assert 'issues' in {'detail': 'Access denied'}
FAILED tests/api/test_api_issues.py::TestIssuesResponseStructure::test_issues_response_contains_issues_array - KeyError: 'issues'
FAILED tests/api/test_api_issues.py::TestIssuesResponseStructure::test_issues_response_total_counts - KeyError: 'total_issues'
FAILED tests/api/test_api_issues.py::TestIssueStructure::test_issue_has_required_fields - KeyError: 'issues'
FAILED tests/api/test_api_issues.py::TestIssueStructure::test_issue_id_is_string - KeyError: 'issues'
FAILED tests/api/test_api_issues.py::TestIssueStructure::test_issue_depends_on_is_array - KeyError: 'issues'
FAILED tests/api/test_api_issues.py::TestIssueStructure::test_issue_proposed_by_is_valid - KeyError: 'issues'
FAILED tests/api/test_api_issues.py::TestIssueStructure::test_issue_timestamps_are_rfc3339 - KeyError: 'issues'
FAILED tests/api/test_api_issues.py::TestIssuesWithTasks::test_issues_include_tasks_query_param - KeyError: 'issues'
FAILED tests/api/test_api_issues.py::TestIssuesWithTasks::test_issue_tasks_is_array - KeyError: 'issues'
FAILED tests/api/test_api_issues.py::TestIssuesWithTasks::test_issue_tasks_count - KeyError: 'issues'
FAILED tests/api/test_api_issues.py::TestTaskStructure::test_task_has_required_fields - KeyError: 'issues'
FAILED tests/api/test_api_issues.py::TestTaskStructure::test_task_id_is_string - KeyError: 'issues'
FAILED tests/api/test_api_issues.py::TestTaskStructure::test_task_depends_on_is_array - KeyError: 'issues'
FAILED tests/api/test_api_issues.py::TestIssuesEndpointEdgeCases::test_issues_without_tasks_query_param - KeyError: 'issues'
FAILED tests/api/test_api_issues.py::TestIssuesEndpointEdgeCases::test_empty_issues_list - KeyError: 'issues'
FAILED tests/api/test_api_metrics.py::TestProjectTokenMetricsEndpoint::test_endpoint_exists - assert 403 == 200
FAILED tests/api/test_api_metrics.py::TestProjectTokenMetricsEndpoint::test_returns_all_usage_records - assert 403 == 200
FAILED tests/api/test_api_metrics.py::TestProjectTokenMetricsEndpoint::test_date_filtering - assert 403 == 200
FAILED tests/api/test_api_metrics.py::TestProjectTokenMetricsEndpoint::test_invalid_date_format_returns_400 - assert 403 == 400
FAILED tests/api/test_api_metrics.py::TestProjectCostMetricsEndpoint::test_endpoint_exists - assert 403 == 200
FAILED tests/api/test_api_metrics.py::TestProjectCostMetricsEndpoint::test_returns_cost_breakdown - assert 403 == 200
FAILED tests/api/test_api_metrics.py::TestAgentMetricsEndpoint::test_returns_agent_metrics - assert 0 == 2
FAILED tests/api/test_api_metrics.py::TestAgentMetricsEndpoint::test_project_filtering - assert 403 == 200
FAILED tests/api/test_api_metrics.py::TestAgentMetricsEndpoint::test_agent_with_no_data_for_project_returns_empty - assert 404 == 200
FAILED tests/api/test_api_metrics.py::TestMetricsEndpointIntegration::test_all_endpoints_consistent - KeyError: 'total_calls'
FAILED tests/api/test_api_prd.py::TestPRDEndpointBasics::test_prd_endpoint_returns_200_when_available - assert 403 == 200
FAILED tests/api/test_api_prd.py::TestPRDResponseStructure::test_prd_response_has_required_fields - AssertionError: assert 'project_id' in {'detail': 'Access denied'}
FAILED tests/api/test_api_prd.py::TestPRDResponseStructure::test_prd_response_project_id_is_string - KeyError: 'project_id'
FAILED tests/api/test_api_prd.py::TestPRDResponseStructure::test_prd_response_timestamps_are_rfc3339 - KeyError: 'generated_at'
FAILED tests/api/test_api_prd.py::TestPRDResponseStructure::test_prd_response_status_is_available - KeyError: 'status'
FAILED tests/api/test_api_prd.py::TestPRDResponseStructure::test_prd_response_contains_correct_content - KeyError: 'prd_content'
FAILED tests/api/test_api_prd.py::TestPRDEndpointNotFound::test_prd_not_found_returns_status_not_found - assert 403 == 200
FAILED tests/api/test_api_prd.py::TestPRDEndpointNotFound::test_prd_not_found_returns_empty_content - KeyError: 'prd_content'
FAILED tests/api/test_api_prd.py::TestPRDEndpointEdgeCases::test_prd_endpoint_with_very_large_content - assert 403 == 200
FAILED tests/api/test_api_prd.py::TestPRDEndpointEdgeCases::test_prd_updated_at_reflects_latest_change - KeyError: 'updated_at'
FAILED tests/api/test_api_session.py::TestSessionEndpoint::test_get_session_success_with_existing_session - assert 403 == 200
FAILED tests/api/test_api_session.py::TestSessionEndpoint::test_get_session_returns_empty_state_when_no_file - assert 403 == 200
FAILED tests/api/test_api_session.py::TestSessionEndpoint::test_session_state_structure_validation - KeyError: 'last_session'
FAILED tests/api/test_api_session.py::TestSessionEndpoint::test_session_handles_corrupted_json - assert 403 == 200
FAILED tests/api/test_api_session.py::TestSessionEndpoint::test_session_timestamp_format - KeyError: 'last_session'
FAILED tests/api/test_api_session.py::TestSessionEndpoint::test_session_next_actions_order_preserved - KeyError: 'next_actions'
FAILED tests/api/test_api_session.py::TestSessionEndpoint::test_session_blocker_structure - KeyError: 'active_blockers'
FAILED tests/api/test_api_session.py::TestSessionEndpoint::test_session_progress_percentage_range - KeyError: 'progress_pct'
FAILED tests/api/test_api_session.py::TestSessionEndpoint::test_session_endpoint_response_time - assert 403 == 200
FAILED tests/api/test_api_session.py::TestSessionEndpointEdgeCases::test_session_with_empty_next_actions - KeyError: 'next_actions'
FAILED tests/api/test_api_session.py::TestSessionEndpointEdgeCases::test_session_with_zero_progress - KeyError: 'progress_pct'
FAILED tests/api/test_api_session.py::TestSessionEndpointEdgeCases::test_session_with_100_percent_progress - KeyError: 'progress_pct'
FAILED tests/api/test_blocker_resolution_api.py::TestBlockerResolveEndpointBasics::test_resolve_endpoint_returns_200_on_success - assert 403 == 200
FAILED tests/api/test_blocker_resolution_api.py::TestBlockerResolveResponseStructure::test_resolve_response_has_required_fields - AssertionError: assert 'blocker_id' in {'detail': 'Access denied'}
FAILED tests/api/test_blocker_resolution_api.py::TestBlockerResolveResponseStructure::test_resolve_response_blocker_id_is_int - KeyError: 'blocker_id'
FAILED tests/api/test_blocker_resolution_api.py::TestBlockerResolveResponseStructure::test_resolve_response_status_is_resolved - KeyError: 'status'
FAILED tests/api/test_blocker_resolution_api.py::TestBlockerResolveResponseStructure::test_resolve_response_timestamp_is_rfc3339 - KeyError: 'resolved_at'
FAILED tests/api/test_blocker_resolution_api.py::TestBlockerResolutionPersistence::test_blocker_status_updated_in_database - AssertionError: assert 'PENDING' == 'RESOLVED'
FAILED tests/api/test_blocker_resolution_api.py::TestBlockerResolutionPersistence::test_answer_stored_in_database - AssertionError: assert None == 'Use JWT for stateless API authentication'
FAILED tests/api/test_blocker_resolution_api.py::TestBlockerResolutionPersistence::test_resolved_at_timestamp_stored - assert None is not None
FAILED tests/api/test_blocker_resolution_api.py::TestBlockerResolutionValidation::test_resolve_accepts_answer_at_max_length - assert 403 == 200
FAILED tests/api/test_blocker_resolution_api.py::TestBlockerResolutionConflicts::test_duplicate_resolution_returns_409 - assert 403 == 200
FAILED tests/api/test_blocker_resolution_api.py::TestBlockerResolutionConflicts::test_duplicate_resolution_preserves_first_answer - AssertionError: assert None == 'Answer 1'
FAILED tests/api/test_blocker_resolution_api.py::TestBlockerResolutionConflicts::test_conflict_response_includes_blocker_id - AssertionError: assert 'blocker_id' in {'detail': 'Access denied'}
FAILED tests/api/test_blocker_resolution_api.py::TestBlockerResolutionConflicts::test_conflict_response_includes_error_message - AssertionError: assert 'error' in {'detail': 'Access denied'}
FAILED tests/api/test_chat_api.py::TestChatEndpoint::test_send_message_success - assert 403 == 200
FAILED tests/api/test_chat_api.py::TestChatEndpoint::test_send_message_agent_not_started - assert 403 == 400
FAILED tests/api/test_chat_api.py::TestChatEndpoint::test_send_message_agent_failure - assert 403 == 500
FAILED tests/api/test_chat_api.py::TestChatHistoryEndpoint::test_get_history_success - assert 403 == 200
FAILED tests/api/test_chat_api.py::TestChatHistoryEndpoint::test_get_history_pagination - assert 403 == 200
FAILED tests/api/test_chat_api.py::TestChatHistoryEndpoint::test_get_history_empty - assert 403 == 200
FAILED tests/api/test_chat_api.py::TestChatWebSocketIntegration::test_chat_broadcasts_message - assert 403 == 200
FAILED tests/api/test_chat_api.py::TestChatWebSocketIntegration::test_chat_continues_when_broadcast_fails - assert 403 == 200
FAILED tests/api/test_discovery_endpoints.py::TestDiscoveryAnswerEndpoint::test_post_discovery_answer_returns_200_with_valid_answer - assert 403 == 200
FAILED tests/api/test_discovery_endpoints.py::TestDiscoveryAnswerEndpoint::test_post_when_not_in_discovery_phase_returns_400 - assert 403 == 400
FAILED tests/api/test_discovery_endpoints.py::TestDiscoveryAnswerEndpoint::test_discovery_not_started_returns_400 - assert 403 == 400
FAILED tests/api/test_discovery_endpoints.py::TestDiscoveryAnswerEndpoint::test_lead_agent_process_discovery_answer_called_correctly - assert 403 == 200
FAILED tests/api/test_discovery_endpoints.py::TestDiscoveryAnswerEndpoint::test_response_includes_required_fields - assert 403 == 200
FAILED tests/api/test_endpoints_database.py::TestProjectsEndpoint::test_list_projects_with_data - assert 0 == 2
FAILED tests/api/test_endpoints_database.py::TestProjectsEndpoint::test_list_projects_returns_all_fields - IndexError: list index out of range
FAILED tests/api/test_endpoints_database.py::TestProjectStatusEndpoint::test_get_project_status_success - assert 403 == 200
FAILED tests/api/test_endpoints_database.py::TestProjectStatusEndpoint::test_get_project_status_returns_complete_data - assert 403 == 200
FAILED tests/api/test_endpoints_database.py::TestAgentsEndpoint::test_get_agents_empty_list - assert 403 == 200
FAILED tests/api/test_endpoints_database.py::TestAgentsEndpoint::test_get_agents_with_data - assert 403 == 200
FAILED tests/api/test_endpoints_database.py::TestAgentsEndpoint::test_get_agents_returns_all_fields - assert 403 == 200
FAILED tests/api/test_endpoints_database.py::TestEndpointDatabaseIntegration::test_complete_project_workflow_via_api - assert False
FAILED tests/api/test_endpoints_database.py::TestEndpointDatabaseIntegration::test_endpoints_survive_multiple_requests - assert False
FAILED tests/api/test_endpoints_database.py::TestProjectTasksEndpoint::test_get_tasks_empty_database - assert 403 == 200
FAILED tests/api/test_endpoints_database.py::TestProjectTasksEndpoint::test_get_tasks_with_data - assert 403 == 200
FAILED tests/api/test_endpoints_database.py::TestProjectTasksEndpoint::test_get_tasks_status_filtering - assert 403 == 200
FAILED tests/api/test_endpoints_database.py::TestProjectTasksEndpoint::test_get_tasks_pagination - assert 403 == 200
FAILED tests/api/test_endpoints_database.py::TestProjectTasksEndpoint::test_get_tasks_total_count_accuracy - assert 403 == 200
FAILED tests/api/test_endpoints_database.py::TestProjectTasksEndpoint::test_get_tasks_edge_cases - assert 403 == 200
FAILED tests/api/test_endpoints_database.py::TestProjectTasksEndpointSecurity::test_get_tasks_valid_max_limit_accepted - assert 403 == 200
FAILED tests/api/test_project_creation_api.py::TestProjectCreationIntegration::test_create_project_via_api_then_get_status - AttributeError: 'dict' object has no attribute 'id'
FAILED tests/api/test_project_reviews.py::TestProjectCodeReviewsEndpoint::test_get_project_code_reviews_success - assert 403 == 200
FAILED tests/api/test_project_reviews.py::TestProjectCodeReviewsEndpoint::test_get_project_code_reviews_with_severity_filter - assert 403 == 200
FAILED tests/api/test_project_reviews.py::TestProjectCodeReviewsEndpoint::test_get_project_code_reviews_multiple_severity_filters - assert 403 == 200
FAILED tests/api/test_project_reviews.py::TestProjectCodeReviewsEndpoint::test_get_project_code_reviews_empty_project - assert 403 == 200
FAILED tests/api/test_project_reviews.py::TestProjectCodeReviewsEndpoint::test_get_project_code_reviews_findings_structure - assert 403 == 200
FAILED tests/api/test_project_reviews.py::TestProjectCodeReviewsEndpoint::test_get_project_code_reviews_no_blocking_issues - assert 403 == 200

[traycerai]

Plan

Observations

All failing API tests are receiving 403 "Access denied" errors instead of expected 200 responses. The root cause is a mismatch between authentication and authorization: when AUTH_REQUIRED=false, the get_current_user dependency returns a default admin user with id=1, but test projects are created without a user_id, resulting in NULL ownership. The user_has_project_access authorization check then fails because the project has no owner and no collaborators, triggering 403 errors across all protected endpoints.

Approach

The fix requires ensuring test projects are associated with the default admin user (user_id=1) so authorization checks pass when AUTH_REQUIRED=false. This can be achieved by modifying the api_client fixture in file:tests/api/conftest.py to set a default user_id=1 for all test database operations, or by updating the Database.create_project method to default to user_id=1 when AUTH_REQUIRED=false. The fixture approach is cleaner as it keeps test-specific logic in test configuration.

Implementation Steps

1. Update API Test Fixture Configuration

File: file:tests/api/conftest.py

Modify the api_client fixture to ensure the default admin user exists and all test projects are associated with this user:

• After setting environment variables (around line 71), add code to ensure the default admin user exists in the database
• Create or verify user with id=1, email='admin@localhost', name='Admin User' in the users table
• This matches the default user returned by get_current_user when AUTH_REQUIRED=false (see file:codeframe/ui/auth.py line 98)

2. Update Database Helper for Tests

File: file:tests/api/conftest.py

Add a helper function or modify the fixture to patch Database.create_project to automatically set user_id=1 for all test project creations:

• After the server reload (around line 78), monkey-patch the database instance's create_project method
• Wrap the original method to inject user_id=1 if not explicitly provided
• This ensures all db.create_project() calls in tests automatically associate projects with the admin user

Alternative approach: Modify each test file to pass user_id=1 explicitly, but this is more invasive and error-prone.

3. Verify Authorization Logic

Files: All router files in file:codeframe/ui/routers/

No changes needed to router files. The authorization checks using db.user_has_project_access(current_user.id, project_id) are correct. They check:

• Project ownership via projects.user_id field
• Collaborator access via project_users table

Once projects have user_id=1, these checks will pass for the default admin user.

4. Test Cleanup Verification

File: file:tests/api/conftest.py

Verify the clean_database_between_tests fixture (lines 92-139) properly cleans the users table:

• Ensure users table is NOT cleared between tests (the default admin user should persist)
• Only clear project-related data (projects, tasks, issues, etc.)
• The current implementation doesn't clear users table, which is correct

5. Validation Approach

Run the failing test suite to verify fixes:

pytest tests/api/test_api_discovery_progress.py -v
pytest tests/api/test_api_issues.py -v
pytest tests/api/test_api_metrics.py -v

All tests should now pass with 200 responses instead of 403 errors.

Implementation Flow

sequenceDiagram
    participant Test as Test Suite
    participant Fixture as api_client Fixture
    participant DB as Database
    participant Auth as get_current_user
    participant Router as API Router
    
    Test->>Fixture: Request api_client
    Fixture->>DB: Initialize database
    Fixture->>DB: Create default admin user (id=1)
    Fixture->>Fixture: Patch create_project to inject user_id=1
    Fixture->>Test: Return configured client
    
    Test->>DB: create_project("test-project")
    Note over DB: Patched method adds user_id=1
    DB->>DB: INSERT INTO projects (user_id=1)
    DB->>DB: INSERT INTO project_users (user_id=1, role='owner')
    
    Test->>Router: GET /api/projects/1
    Router->>Auth: get_current_user()
    Note over Auth: AUTH_REQUIRED=false
    Auth->>Router: User(id=1, email='admin@localhost')
    Router->>DB: user_has_project_access(user_id=1, project_id=1)
    DB->>Router: True (user owns project)
    Router->>Test: 200 OK with project data

Loading

Key Files to Modify

File	Changes	Priority
file:tests/api/conftest.py	Add default admin user creation and patch create_project	High
All test files in file:tests/api/	No changes needed (benefit from fixture updates)	N/A

Expected Outcomes

• All 100+ failing API tests will pass
• Projects created in tests will have user_id=1
• Authorization checks will succeed for default admin user
• No changes needed to production code
• Test isolation maintained through existing cleanup fixture

Import In IDE

🤖 Prompt for AI Agents

## Observations

All failing API tests are receiving 403 "Access denied" errors instead of expected 200 responses. The root cause is a mismatch between authentication and authorization: when `AUTH_REQUIRED=false`, the `get_current_user` dependency returns a default admin user with `id=1`, but test projects are created without a `user_id`, resulting in `NULL` ownership. The `user_has_project_access` authorization check then fails because the project has no owner and no collaborators, triggering 403 errors across all protected endpoints.

## Approach

The fix requires ensuring test projects are associated with the default admin user (`user_id=1`) so authorization checks pass when `AUTH_REQUIRED=false`. This can be achieved by modifying the `api_client` fixture in `file:tests/api/conftest.py` to set a default `user_id=1` for all test database operations, or by updating the `Database.create_project` method to default to `user_id=1` when `AUTH_REQUIRED=false`. The fixture approach is cleaner as it keeps test-specific logic in test configuration.

## Implementation Steps

### 1. Update API Test Fixture Configuration

**File:** `file:tests/api/conftest.py`

Modify the `api_client` fixture to ensure the default admin user exists and all test projects are associated with this user:

- After setting environment variables (around line 71), add code to ensure the default admin user exists in the database
- Create or verify user with `id=1`, `email='admin@localhost'`, `name='Admin User'` in the users table
- This matches the default user returned by `get_current_user` when `AUTH_REQUIRED=false` (see `file:codeframe/ui/auth.py` line 98)

### 2. Update Database Helper for Tests

**File:** `file:tests/api/conftest.py`

Add a helper function or modify the fixture to patch `Database.create_project` to automatically set `user_id=1` for all test project creations:

- After the server reload (around line 78), monkey-patch the database instance's `create_project` method
- Wrap the original method to inject `user_id=1` if not explicitly provided
- This ensures all `db.create_project()` calls in tests automatically associate projects with the admin user

Alternative approach: Modify each test file to pass `user_id=1` explicitly, but this is more invasive and error-prone.

### 3. Verify Authorization Logic

**Files:** All router files in `file:codeframe/ui/routers/`

No changes needed to router files. The authorization checks using `db.user_has_project_access(current_user.id, project_id)` are correct. They check:
- Project ownership via `projects.user_id` field
- Collaborator access via `project_users` table

Once projects have `user_id=1`, these checks will pass for the default admin user.

### 4. Test Cleanup Verification

**File:** `file:tests/api/conftest.py`

Verify the `clean_database_between_tests` fixture (lines 92-139) properly cleans the users table:

- Ensure users table is NOT cleared between tests (the default admin user should persist)
- Only clear project-related data (projects, tasks, issues, etc.)
- The current implementation doesn't clear users table, which is correct

### 5. Validation Approach

Run the failing test suite to verify fixes:

```bash
pytest tests/api/test_api_discovery_progress.py -v
pytest tests/api/test_api_issues.py -v
pytest tests/api/test_api_metrics.py -v
```

All tests should now pass with 200 responses instead of 403 errors.

## Implementation Flow

```mermaid
sequenceDiagram
    participant Test as Test Suite
    participant Fixture as api_client Fixture
    participant DB as Database
    participant Auth as get_current_user
    participant Router as API Router
    
    Test->>Fixture: Request api_client
    Fixture->>DB: Initialize database
    Fixture->>DB: Create default admin user (id=1)
    Fixture->>Fixture: Patch create_project to inject user_id=1
    Fixture->>Test: Return configured client
    
    Test->>DB: create_project("test-project")
    Note over DB: Patched method adds user_id=1
    DB->>DB: INSERT INTO projects (user_id=1)
    DB->>DB: INSERT INTO project_users (user_id=1, role='owner')
    
    Test->>Router: GET /api/projects/1
    Router->>Auth: get_current_user()
    Note over Auth: AUTH_REQUIRED=false
    Auth->>Router: User(id=1, email='admin@localhost')
    Router->>DB: user_has_project_access(user_id=1, project_id=1)
    DB->>Router: True (user owns project)
    Router->>Test: 200 OK with project data
```

## Key Files to Modify

| File | Changes | Priority |
|------|---------|----------|
| `file:tests/api/conftest.py` | Add default admin user creation and patch `create_project` | High |
| All test files in `file:tests/api/` | No changes needed (benefit from fixture updates) | N/A |

## Expected Outcomes

- All 100+ failing API tests will pass
- Projects created in tests will have `user_id=1`
- Authorization checks will succeed for default admin user
- No changes needed to production code
- Test isolation maintained through existing cleanup fixture

---

Execution Information

Branch: main
Commit: 2197fea

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• [Phase 3→4] Add edge case testing across core components #114
• Backend: Checkpoint creation endpoint ignores project_id parameter #89
• Fix checkpoint panel visibility - CheckpointList not rendering items #85
• [P2] Replace mocked unit tests with real integration tests #113

🔗 Related PRs

#22 - fix: Reorganize test suite and fix API test failures [merged]
#25 - feat: Discovery Answer UI Integration (Feature 012) [merged]
#28 - feat: Complete session lifecycle implementation and fix integration tests [merged]
#38 - fix(e2e): Improve Playwright test pass rate from 18% to 57% [merged]
#83 - refactor: Extract FastAPI routers for improved maintainability (94% reduction in server.py) [merged]

👤 Suggested Assignees

• frankbria

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[frankbria]

Fixed in commit 921fa70. All 187 API tests now passing (100% pass rate).

Changes:

• Fixed 403 authorization errors by ensuring test projects have proper ownership
• Fixed API router type mismatch (dict vs object attributes)
• Corrected test expectations to match actual API behavior

Results:

• Before: 180/187 tests passing (7 failures)
• After: 187/187 tests passing (100% success rate)

Files Modified:

• tests/api/conftest.py - Authorization fixture with default admin user
• codeframe/ui/routers/projects.py - Dict access instead of object attributes
• tests/api/test_api_metrics.py - Corrected field names and test data