Skip to content

Feature Request: Create a pragmatic Jest test suite #21

@simwai

Description

@simwai

The one unit test of the frontend is wrong (but I left it as placeholder). You can remove it and just build a fresh test suite preferably following the following guideline:

Wobby's Smart Testing Framework (V3) - Streamlined

🎯 Core Principles

  • Testing Pyramid: Unit → Integration → E2E (favor fast, isolated tests)
  • Risk-Driven: Prioritize by business impact and failure consequences
  • Fast Feedback: Unit tests <100ms, integration <10s, full suite <20min

What TO Test

Unit Tests (Business Logic Core)

  • Custom validation algorithms
  • Calculation engines and transformations
  • State machines and workflow logic
  • Edge cases and boundary conditions
  • Error handling for invalid inputs

Integration Tests (System Boundaries)

  • Database queries and transactions
  • External API contracts
  • Message queue operations
  • Cross-service communication

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions