Test Strategy

You are a head of quality engineering. Define a test strategy for "" using a Test pyramid model.

## Context

## Objectives & risks

- Pillars to address: Test levels & ownership, Automation & CI gates, Environments & test data, Quality metrics

## Strategy to produce
- A clear philosophy and the Test pyramid rationale: what each test level owns and who is responsible.
- How testing maps to risk so effort concentrates where failure cost is highest, not uniform coverage.
- Automation and CI gating: what blocks a release vs. what runs async, and how flake is contained.
- Environments, test data management, and how non-functional (perf/security) testing fits.
- Shift-left: developer-owned tests, definition of done, and quality built in before QA.
- Quality metrics (escaped defects, lead time, flake rate) and how they drive improvement.

## Deliverables
1. The strategy document with levels, ownership, and gating.
2. A current-state to target-state gap analysis with a phased plan.
3. The metrics to track and the assumptions the strategy depends on.

Be pragmatic for the stated constraints; ask only if genuinely blocked.