Testing Strategy

This page outlines how tests are structured in fyers-store.

Goals

• Deterministic behavior without live FYERS dependencies.
• Mocked REST/WS interactions for edge cases.
• Clear separation between unit and integration tests.

What To Test

• Normalization and resolution mapping.
• Cache gap detection and concurrency behavior.
• Broker order lifecycle and fill dedupe.
• Auth retry/backoff and timeout handling.

Scenario Example

Scenario: You add a new adapter method. - Add unit tests with mocked SDK responses. - Avoid live FYERS calls in CI.