Initial test around stampy.ts

[jrhender]

This PR uses the miniflare jest env (https://miniflare.dev/testing/jest) to run a test on code that has a dependency on CF workers, in this case server-utils/stampy.ts.

The new test, in stampy.spect.ts, relies on a data which is stored in the repository in the mocks directory.
The data can be refreshed manually by running npm run refresh-test-data.

The only app code change (other than new exports) a cut-paste of Coda URL generation from stampy.ts to a separate file. Other wise, compilation of the refresh coda data script fails due to missing CF vars (e.g. CODA_TOKEN).

TODO:

• ensure that latest code is being tested (as it seems to be the built CF worker file that is executed)
• add script for generating test data
• write README on how to use the script
• parameterize the test to run for each result of the mock data
• share the same question ids between the script and the test (was too challenging to get the compilation to work)
• use questionId 0 for test
• manually run app to do basic sanity test (e.g. can app still get question details from Coda)

Relates to issue #191

[jrhender]

@Aprillion I think all of the comments from your first review have been addressed. Please give the PR another review when you have the opportunity (no rush at all 😄 ).

[jrhender]

@Aprillion The PR is ready for review again when you have time. No rush.

[jrhender]

Hey @Aprillion, no rush, but just checking in here. What would you say the next steps for this PR would be? Are there additional reviews or changes required?
If it is indeed ready and it is a good time to merge, could you please do so when you have capacity? I don't currently have write access to the repo, so I can't merge it myself.

[Aprillion]

oh, GH actions needed some extra approval, not just PR approval.. the merge button should get enabled after the checks run I hope..

[Aprillion]

@jrhender one of the tests failed in https://github.com/StampyAI/stampy-ui/actions/runs/6245510948/job/17457463802?pr=276#step:3:139 FAIL app/server-utils/stampy.spec.ts -> loadQuestionDetail › can load question 0, can you please check?

[jrhender]

@Aprillion could you approval the workflow again when you have a moment please?
I think the issue was that the feature branch (miniflare-jest-env) didn't have the last changes so it was trying to make a request to Coda that probably wasn't available due to some change in Coda. I thought about merging in master before posting my earlier message but I was too lazy to do so 😓 .
At any rate, the CI is now passing on my GH fork (https://github.com/jrhender/stampy-ui/actions/runs/6435300979/job/17476259392?pr=2), so I'm pretty sure it will pass now in this PR.

[jrhender]

Whoops, sorry, I guess it needs to be reviewed again as well as I updated the cached coda data in the last commit: 30845a9

[Aprillion]

the tests are green for me locally too, no idea why it fails in the GH actions of the main repo 🤔

let's try to merge and see if the tests will start working for next PR - and if now, we will disable and investigate later 🤷

[Aprillion]

ok, the test passed for PR #337 => https://github.com/StampyAI/stampy-ui/actions/runs/6439654334/job/17487581099?pr=337

😌