mukimovd/turash
1
0
Fork 0
mirror of https://github.com/SamyRai/turash.git synced 2025-12-26 23:01:33 +00:00
Code Issues 1 Actions Packages Projects Releases Wiki Activity
3ddf8e2624
turash/docs/concept/16_testing_strategy.md
Damir Mukimov 000eab4740
Major repository reorganization and missing backend endpoints implementation 
Repository Structure:
- Move files from cluttered root directory into organized structure
- Create archive/ for archived data and scraper results
- Create bugulma/ for the complete application (frontend + backend)
- Create data/ for sample datasets and reference materials
- Create docs/ for comprehensive documentation structure
- Create scripts/ for utility scripts and API tools

Backend Implementation:
- Implement 3 missing backend endpoints identified in gap analysis:
  * GET /api/v1/organizations/{id}/matching/direct - Direct symbiosis matches
  * GET /api/v1/users/me/organizations - User organizations
  * POST /api/v1/proposals/{id}/status - Update proposal status
- Add complete proposal domain model, repository, and service layers
- Create database migration for proposals table
- Fix CLI server command registration issue

API Documentation:
- Add comprehensive proposals.md API documentation
- Update README.md with Users and Proposals API sections
- Document all request/response formats, error codes, and business rules

Code Quality:
- Follow existing Go backend architecture patterns
- Add proper error handling and validation
- Match frontend expected response schemas
- Maintain clean separation of concerns (handler -> service -> repository)
2025-11-25 06:01:16 +01:00

1.8 KiB
Raw Blame History

14. Testing Strategy

Recommendation: Comprehensive testing pyramid.

Testing Layers

  1. Unit Tests (70% coverage target):

    • Business logic functions (100% coverage)
    • Matching algorithms (95% coverage, focus on edge cases)
    • Economic calculations (100% coverage, ±€0.01 accuracy)
    • Data validation (100% coverage, all error paths)

  2. Integration Tests (20% of test suite):

    • API endpoints (200+ test cases, all CRUD operations)
    • Database operations (Neo4j + PostgreSQL integration)
    • Event processing (Watermill pubsub reliability)
    • Service integrations (external APIs, IoT devices)

  3. E2E Tests (10% of test suite):

    • Critical user flows (match discovery → connection → implementation)
    • Match discovery and connection flow (85% success rate target)
    • Payment processing (Stripe integration, transaction success rate >99.5%)
    • Cross-browser compatibility (Chrome, Firefox, Safari, Edge)

Testing Tools

  • Backend:
    • Built-in testing package (Go 1.25 improvements)
    • github.com/stretchr/testify: Assertions, suites, mocks
    • github.com/golang/mock or github.com/vektra/mockery/v2: Mocking
  • API Testing:
    • net/http/httptest: Built-in HTTP testing
    • github.com/go-resty/resty/v2: For integration tests
  • E2E: Playwright or Cypress
  • Graph Database Testing:
    • Testcontainers: github.com/testcontainers/testcontainers-go
    • Neo4j test container setup
  • Load Testing:
    • k6 (Go-based, recommended)
    • github.com/tsenart/vegeta: HTTP load testing library
  • Benchmarking: Built-in go test -bench

Test Data Strategy

  • Fixtures: Realistic test data generators
  • Test Database: Isolated test environment
  • Snapshots: Graph database snapshots for integration tests
  • Mocking: External APIs (government registries, payment providers)