Skip to content

Conversation

@struan
Copy link
Member

@struan struan commented Dec 4, 2025

This adds a dummy DaDem, plus GAZE and Ratty endpoint that fakes things
well enough to allow local testing without access to those services.
It's still a bit fragile but in general it works well enough when run
with Docker to allow you to do the whole thing.

Currently you have to log in to the container and start fyrqd by hand
for things to work.

The results on the candiated choice screen are somewhat unrealistic but
the point is more to let you run through the screens.

The actual script is outside the web tree and mapped in by Docker so
won't be accidentally discoverable live.

@struan struan requested review from ajparsons and dracos December 4, 2025 15:28
Copy link
Member

@dracos dracos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine with me; we should probably also move away from having to deploy a test on a server, but eh when do we have time for that. This seems easier than letting WTT use mocked instances or something, doesn' t it

struan added 2 commits January 5, 2026 13:31
This adds a dummy DaDem, plus GAZE and Ratty endpoint that fakes things
well enough to allow local testing without access to those services.
It's still a bit fragile but in general it works well enough when run
with Docker to allow you to do the whole thing.

Currently you have to log in to the container and start fyrqd by hand
for things to work.

The results on the candiated choice screen are somewhat unrealistic but
the point is more to let you run through the screens.

The actual script is outside the web tree and mapped in by Docker so
won't be accidentally discoverable live.
@struan struan force-pushed the dev-friendly-version branch from 80693fa to cd78610 Compare January 5, 2026 13:31
Start in right directory, prompt for MAPIT_API_KEY
Returns answers that are a bit responsive to area type, meaning it can be tested on different parts of the map.
@ajparsons
Copy link
Contributor

Ok - see what you think of this. This now seems to work for me in my docker.

I've moved the packages that were needed to run fyrqd into the packages file (conversation with Sam says this currently isn't used in production, just development).

The more fiddly change was making the dadem dummy data a bit more responsive to different areas (I tried to test with london postcodes and it started throwing mismatch errors because the results being returned in the dummy data didn't line up with the areas it expected). I might have missed something more simple though.

Copy link
Member Author

@struan struan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one small fix but this looks decent

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants