SkillVaultskills Browse all 1,000+ skills

Testing · Version 1.0.0 · Reviewed 2026-08-02

Phoenix Test Strategy Specialist

Design confidence for phoenix risk-based test design and phoenix integration boundary coverage with evidence, explicit trade-offs, and a verification plan.

4 method steps 6 documented failure modes 5 diagnostic checks 7 quality gates

Builds a risk-based test portfolio around the real failure mechanisms of Phoenix using router, supervision tree, LiveView processes, channels, and Ecto queries and telemetry events, process mailboxes, query timing, and LiveView diffs, with explicit attention to a long-lived socket process accumulating state or messages without a bounded lifecycle.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • Phoenix risk-based test design
  • Phoenix integration boundary coverage
  • Phoenix regression gate definition

How Phoenix Test Strategy Specialist works

You provide

Suite structure, failure history, and the risk to cover

It inspects

Nondeterminism sources affecting phoenix risk-based test design

It decides

A phoenix integration boundary coverage plan at the cheapest useful level

You verify

The test fails when the behavior is broken, not only passes

What it checks first

Phoenix Test Strategy Specialist builds a risk-based test portfolio around the real failure mechanisms of Phoenix using router, supervision tree, LiveView processes, channels, and Ecto queries and telemetry events, process mailboxes, query timing, and LiveView diffs, with explicit attention to a long-lived socket process accumulating state or messages without a bounded lifecycle. Use it when the work involves Phoenix risk-based test design, Phoenix integration boundary coverage, Phoenix regression gate definition.

  1. Whether the test asserts behavior or implementation, because implementation-coupled tests break on safe refactors.
  2. Sources of nondeterminism: time, randomness, ordering, concurrency, network, and shared state.
  3. Whether tests share mutable state, which makes failures depend on execution order.
  4. The test pyramid balance, since a suite dominated by end-to-end tests is slow and flaky by construction.
  5. Whether a failing test failed for the intended reason, verified by making it fail deliberately.

Failure modes it recognizes

  • A flaky test caused by a fixed sleep instead of waiting for the actual condition.
  • Tests passing in isolation and failing in suite because of leaked global or database state.
  • Time-dependent assertions failing at month or year boundaries or across daylight-saving transitions.
  • Over-mocking that verifies the mock rather than the integration, so the suite passes while production breaks.
  • A test asserting on unordered collection order, which passes until the implementation changes hashing.
  • Coverage measured but assertions absent, so lines execute without being verified.

Answers it will reject

  • Retrying a flaky test to make CI green, which converts a real intermittent bug into an invisible one.
  • Chasing a coverage percentage, which produces tests that execute code without asserting behavior.
  • Writing an end-to-end test for logic that a unit test could cover deterministically and instantly.
  • Deleting a failing test to unblock a release without recording the risk that was accepted.

Decision rules it applies

  • Choose the cheapest test level that can actually observe the failure mode.
  • A flaky test is a defect in the test or the system; quarantine with an owner and a deadline, never ignore.
  • Assert on observable behavior and public contracts so refactors stay free.
  • Every bug fix gets a test that fails before the fix and passes after it.

Evidence it asks for

  • Run the suite in randomized order to expose inter-test dependencies.
  • Track flake rate per test over time rather than treating each failure as isolated.
  • Verify a new test fails when the behavior is broken, not only that it passes when correct.

The method inside

  1. Translate phoenix risk-based test design into observable risks and falsifiable acceptance criteria.
  2. Choose the cheapest test level that can expose failures in phoenix integration boundary coverage.
  3. Add representative positive, negative, boundary, and regression cases for phoenix regression gate definition.
  4. Define deterministic pass/fail signals, ownership, and the release decision when a check fails.

Deliverables

  • Phoenix risk-based test design assessment
  • Phoenix integration boundary coverage decision and action plan
  • Phoenix regression gate definition verification checklist

Evidence requirements

  • System risks and architecture boundaries
  • Existing tests, failures, and coverage evidence
  • Release cadence and supported environments

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Apply the test strategy specialist to our Phoenix system before the next production change. We can provide router, supervision tree, LiveView processes, channels, and Ecto queries; the main concern is a long-lived socket process accumulating state or messages without a bounded lifecycle.

Expected output

Make a long-lived socket process accumulating state or messages without a bounded lifecycle the first negative case rather than adding broad happy-path coverage. Exercise process lifecycle, sockets, database transactions, and PubSub delivery at the cheapest level that still uses the real contract, then prove the test fails when the mechanism is reintroduced and remains deterministic under repetition.

Boundaries and compatibility

Ideal for

  • Phoenix risk-based test design: produce a decision or artifact grounded in supplied evidence.
  • Phoenix integration boundary coverage: produce a decision or artifact grounded in supplied evidence.
  • Phoenix regression gate definition: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Chasing line coverage without risk coverage
  • Replacing integration evidence with mocks

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.