Commit eco data fixtures #89

Closed
opened 2026-07-06 17:31:27 +00:00 by coilysiren · 2 comments
Owner
No description provided.
Author
Owner

Unpack it into json and then scramble all the usernames

The apply strict formatting on the json - and format it for human readability so I can check it against the UI

Unpack it into json and then scramble all the usernames The apply strict formatting on the json - and format it for human readability so I can check it against the UI
Owner

Closing this older fixture plan as superseded by #128.

The repository now has a complete snapshot harness that captures every Eco endpoint, stores snapshots privately in S3, and replays them locally through ward exec snapshot-pull, snapshot-serve, and http-offline. .snapshots/ is deliberately gitignored because the source contains player names and other live world state.

Committed tests already use synthetic, reviewable fixtures for stable contracts. Adding a hand-scrambled live dump would create a second fixture system, lose reproducibility when the scrambling changes joins, and require repeated human privacy review.

The selected boundary is private full-fidelity snapshots for integration work plus synthetic committed fixtures for tests. No live dataset should be added to git.

Closing this older fixture plan as superseded by #128. The repository now has a complete snapshot harness that captures every Eco endpoint, stores snapshots privately in S3, and replays them locally through `ward exec snapshot-pull`, `snapshot-serve`, and `http-offline`. `.snapshots/` is deliberately gitignored because the source contains player names and other live world state. Committed tests already use synthetic, reviewable fixtures for stable contracts. Adding a hand-scrambled live dump would create a second fixture system, lose reproducibility when the scrambling changes joins, and require repeated human privacy review. The selected boundary is private full-fidelity snapshots for integration work plus synthetic committed fixtures for tests. No live dataset should be added to git.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-gaming/eco-app#89
No description provided.