I was gonna use miniflare jest to test

I was gonna use miniflare-jest to test my worker by making fetch requests to it, as seen in https://miniflare.dev/testing/jest#writing-and-running-tests. I guess we could call theses "integration tests". Can you confirm this is the right way (I guess so, given the doc).

vvoOP•5/4/23, 9:46 AM

And then have a few more involved tests like:

deploy to cloudflare
make actual fetch requests to cloudflare

vvoOP•5/4/23, 9:46 AM

(but this would not use miniflare)

DaniFoldi•5/4/23, 9:47 AM

There is no single right way to do tests - depends on what you want to make sure doesn't break. It is a possibility to test the external (http) interface of your worker, and if that fails then you know in advance your API would have breaking changes, for example

vvoOP•5/4/23, 9:50 AM

Yup that's the goal

DaniFoldi•5/4/23, 9:51 AM

I personally have 3 layers of tests (not every app needs that, this is an extreme case for an example here)

test the flow of REST API (e2e tests)
test the interface of HTTP endpoints (integration tests, sort of)
test components, utility functions (unit tests)

DaniFoldi•5/4/23, 9:51 AM

in other cases, I'll only do the 2nd, for simple projects I don't really care about internals changing (esp if I'm the only one working on it)

vvoOP•5/4/23, 9:51 AM

test the flow of REST API (e2e tests)

Do you achieve this via wrangler publish --route or similar (to avoid conflicts with production/other PRs) and then run tests on that?

vvoOP•5/4/23, 9:52 AM

test the interface of HTTP endpoints (integration tests, sort of)

=> done via miniflare?

DaniFoldi•5/4/23, 9:56 AM

I run all of these locally with vitest, which is similar to jest, just integrates better with vite

vvoOP•5/4/23, 9:58 AM

You said "e2e tests" so I thought you 1. deploy to cloudflare 2. test the endpoint