4 replies

MrBBot 4470 I m writing tests `vitest

@mrbbot I'm writing tests (

vitest-environment-miniflare

vitest-environment-miniflare

vitest-environment-miniflare

vitest-environment-miniflare) for a worker that binds another worker. The other worker has a DO, and I've bound that DO to the original worker as well. I want to seed an instance of the DO for tests, but I'm running into trouble because constructing that DO requires the other worker's

env

env

env

env (to fetch another bound worker). Is there a way to get the other

env

env

env

env, or a different pattern I should be using to seed the DO?

MrBBot•4/6/23, 10:58 AM

Hey!

Could you add a Durable Object namespace binding to the other DO in your test worker, then use the standard (await env.NAMESPACE.get(id)).fetch("/seed")(await env.NAMESPACE.get(id)).fetch("/seed"), where /seed/seed is some special URL defined in your DO's fetchfetch handler that seeds the required data?

TravisFrankOP•4/6/23, 11:17 AM

Just tried this. Unfortunately the error persists, it looks like the service binding to the third worker isn’t showing up on the env of the DO constructor call

TravisFrankOP•4/6/23, 11:21 AM

The env of worker #2 (the one with the DO) has a service binding to worker #3 that I'm fetching in the constructor of the DO. I'm getting TypeError: Cannot read properties of undefined (reading 'fetch')TypeError: Cannot read properties of undefined (reading 'fetch') when getting the DO, and after inspecting the

env

env

in the DO, I'm noting it's receiving the

env

env

of worker #1 (which does not have a service binding to worker #3).

TravisFrankOP•4/6/23, 1:26 PM

Ahhhh, is this expected behavior? If I fetch a DO declared in another worker, will the DO receive the

env

env

of the calling worker?

MrBBot•4/6/23, 1:26 PM

That shouldn't be the case, it should be receiving the

env

env

of the Worker it's defined in

MrBBot 4470 I m writing tests `vitest

Similar Threads

Similar Threads

Similar Threads