Hey
Thanks for shipping #155 in 1.19.0, the recorded layout is great
I think only half of it landed though. The recorder writes to <fixturePath>/<slugified-testId>/<provider>.json, but the loader is still flat. On boot it just skips every recorded dir:
[fixture-loader] Skipping subdirectory .../greeting--agent-replies-to-a-plain-greeting--no-tools (fixtures are not loaded recursively)
[fixture-loader] Skipping subdirectory .../hitl--hitl-approval-is-required-before-the-agent-runs-a-query (fixtures are not loaded recursively)
aimock server listening on http://127.0.0.1:4010
So record produces the new layout but replay can't read it back, the suite runs against zero fixtures
Could loadFixturesFromDir recurse one level into <testId>/<provider>.json so the read path matches what the recorder writes?
Or move the provider into the json e.g. { "openai": { "fixtures" or { "fixtures": { "openai" and use <testId>.json as name
Hey
Thanks for shipping #155 in 1.19.0, the recorded layout is great
I think only half of it landed though. The recorder writes to
<fixturePath>/<slugified-testId>/<provider>.json, but the loader is still flat. On boot it just skips every recorded dir:So record produces the new layout but replay can't read it back, the suite runs against zero fixtures
Could
loadFixturesFromDirrecurse one level into<testId>/<provider>.jsonso the read path matches what the recorder writes?Or move the provider into the json e.g.
{ "openai": { "fixtures"or{ "fixtures": { "openai"and use<testId>.jsonas name