Install any skill in seconds. Free to start, no credit card required.
Get Started Free →oliver-kriska/testing
Write or repair Elixir tests with ExUnit, sandbox isolation, async reliability, Mox, ExMachina, and LiveViewTest.
Passed 11 of 22 test cases with the skill, and 11 of 22 without it.
1 fixed20 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
We are testing an Ash Framework resource in an Elixir application. A team member is writing direct Repo calls inside test helpers to query and assert resource states. What test case and testing approach should be used for Ash projects?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends using DataCase with Ash.Test helpers for Ash project tests | Missed | Passed |
| Advises testing actions via domain code interfaces rather than direct Repo calls | Passed | Passed |
The instructions your model reads when the skill loads.
Ash projects: Use
DataCasewithAsh.Testhelpers; test actions via domain code interfaces, not directRepocalls. Seeash-frameworkskill.
Quick reference for Elixir testing patterns.
async: true unless tests modify global state@callback behaviourbuild/2 in factories; insert/2 only when DB neededassert_receive with timeout for async operationsvalidate_required in the schema changeset. Missing fields cause cascading test failures| Testing | Use |
|---|---|
| Controller/API | use MyAppWeb.ConnCase |
| Context/Schema | use MyApp.DataCase |
| LiveView | use MyAppWeb.ConnCase + import Phoenix.LiveViewTest |
| Pure logic | use ExUnit.Case, async: true |
Application.put_envtest cases passed, vs 11 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.