Codex Test Phoenix Async Completion with ExUnit Messages
Choose the right Phoenix test case and assert an observable completion signal for local asynchronous work.
中文Install in Codex
Use a Phoenix or Elixir project where `mix test` runs locally.
- Copy the pinned `skills/elixir-phoenix-testing/` directory into `.agents/skills/elixir-phoenix-testing/` in the project.
- Read `references/exunit-patterns.md` in Codex and determine whether the behavior is pure, database-backed, or a LiveView interaction.
Example task
Test a local CSV summary task that sends `{:summary_ready, 3}` to the test process. Use `assert_receive` to verify the three processed rows.What to check
The test waits for the completion message and distinguishes the expected count, an incorrect count, and timeout.
Original SKILL.md on GitHub · Updated
Frequently asked question
When should a fixture actually be inserted?
Insert it when verifying persistence, database identifiers, constraints, or associations. Build an in-memory fixture for pure logic.