test(client): run functional tests in Data Proxy simulator

[aqrln]

It is now possible to use pnpm test:functional --data-proxy or pnpm test:functional --data-proxy --edge-client to run the functional tests in Mini-Proxy — the local Data Proxy simulator specifically made for use in tests (internal: repo).

It is similar to how, e.g., Cloudflare has Miniflare, but is an internal tool for now.

Although it doesn't share any code or architecture with the actual Data Proxy and is significantly simpler implementation of the Data Proxy API, the expectation is it should be a reasonable approximation for use in Prisma Client tests and allow us to have more confidence in the DataProxyEngine code and faster feedback loop. However, it is still essential to have ecosystem-tests running with the real Data Proxy.

Note: bash and openssl need to be installed and available in PATH for this to work on Windows.

Closes https://github.com/prisma/client-planning/issues/80

---

Use this to make some diffs in tests manageable to read:

[Jolg42]

Note:

• packages/client/helpers/mini-proxy/index.js
• packages/client/helpers/mini-proxy/mini-proxy.js

Seems to be build artifacts and could be removed from git? But maybe it's only possible once it's moved in a separate package?

[Jolg42]

Could you run the tests here too?
https://github.com/prisma/prisma/blob/main/.buildkite/publish/run.sh#L24-L32
https://github.com/prisma/prisma/blob/main/.buildkite/test/run.sh#L40-L45

[aqrln]

@Jolg42 they are build artifacts, yes. I left comments about them above. They will be removed once mini-proxy is on npm.

[aqrln]

@Jolg42

Could you run the tests here too?
https://github.com/prisma/prisma/blob/main/.buildkite/publish/run.sh#L24-L32
https://github.com/prisma/prisma/blob/main/.buildkite/test/run.sh#L40-L45

Good point about the publish pipeline.

I didn't run it in the test pipeline on Buildkite intentionally and added Node.js 14 to the matrix on GitHub Actions instead to avoid running it twice (once with PRISMA_CLIENT_ENGINE_TYPE=binary and once with PRISMA_CLIENT_ENGINE_TYPE=library, which would be irrelevant and only waste CPU time). But it still needs to be run in the publish pipeline I think.

[Jolg42]

Discussed offline:
We can ignore adding it to Buildkite, the only benefit would be that we run Node.js 14 on Buildkite but this will be tested on Node.js 14 on GitHub actions.