Files
blog.pyaqa.ru/tests/TEST_MODEL.md
Sergey Vanyushkin c9b380c601 test(api): add full API test suite with get_keycloak_client async fix
Add 45 API tests covering all 12 post endpoints (CRUD, publish/unpublish) with RBAC policy coverage across guest, user, admin roles.

Fix get_keycloak_client() in deps.py to be async - Dishka's async container requires await on get(), without it a coroutine object was returned instead of the actual client.
2026-05-10 11:21:58 +00:00

2.7 KiB

Test Model: Blog

Global test coverage map for the blog application. Use this file to assess which features are covered, where gaps exist, and what to prioritize when adding new tests.

Coverage Matrix

Feature Unit Integration API E2E Priority Status
Post Lifecycle (CRUD, Publish) 85% 90% 70% P0 Active
RBAC & Access Control 100% 90% 60% P0 Active
Domain Value Objects 100% P0 Stable
Domain Entities 95% P0 Stable
Domain Exceptions 100% P1 Stable
List & Search Posts 70% P1 ⚠️ Partial
Keycloak Auth Client 80% P0 Active
App Bootstrap & Config 75% P1 Stable
Transaction Manager 60% P2 ⚠️ Partial
Web UI Error Handling 50% P1 ⚠️ Partial
Pagination 40% 60% P1 ⚠️ Partial
Post Edit via Web 40% P1 ⚠️ Partial
Post Delete via Web 40% P1 ⚠️ Partial

Legend: Covered / ⚠️ Partial / Missing / — Not Applicable

Feature Files

Feature Model File
Post Lifecycle FEATURE_POST_LIFECYCLE.md
RBAC & Access Control FEATURE_RBAC.md
Domain Foundation FEATURE_DOMAIN_FOUNDATION.md
Infrastructure & Bootstrap FEATURE_INFRASTRUCTURE.md

Test Naming Convention

  • TC-UNIT-NNN: Unit test case
  • TC-E2E-NNN: End-to-end test case
  • TC-INT-NNN: Integration test case
  • TC-API-NNN: API test case

How to Update This Model

  1. When adding a new test, assign the next available TC-ID in the relevant feature file.
  2. Update the Coverage Matrix above if the new test closes a gap or changes coverage percentage.
  3. Update the Last Verified field in the feature file after running the test successfully.
  4. When a test is deleted or renamed, update the corresponding TC entry and mark it as Deprecated.

Risk Areas

  1. No Integration Tests: SQLAlchemy repository has no integration tests against a real database.
  2. Restored API Tests: API endpoint tests restored in tests/api/ covering all CRUD, publish/unpublish, and RBAC policies.
  3. Web UI Error Handling: Only covered indirectly via E2E; no dedicated error-scenario E2E tests.
  4. Pagination Edge Cases: Page boundaries, empty pages, and large offsets are not explicitly tested.
  5. Edit/Delete Web Flows: No E2E coverage for editing or deleting posts through the web UI.