V
P
L
cloudflare:test
Doc-testing – Why do these examples look like tests?
1L
routeDORequestagents
L
V
PX11
agentsagents
E
S
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
J i noticed that errors thrown from functions called across a workers RPC boundary don't contain the original stack trace (for example when calling a function on a durable object stub or a service binding)N
G
G
VL1VG1
LL1L1PP1P1PP1P11
I1P1IPP
/cfrole@lumenize/testingjson-rpc-mixinjson-rpc-mixinjson-rpc-mixinjson-rpc-mixinrouteAgentRequest{ cors: true }{ cors: true }lumenize{ cors: false}it('shows basic 5-step test', async () => {
// 1. Create RPC testing client and Browser instance
await using client = createTestingClient<MyDOType>('MY_DO', '5-step');
const browser = new Browser();
// 2. Pre-populate storage via RPC to call asycn KV API
await client.ctx.storage.put('count', 10);
// 3. Make a fetch and RPC call to increment
const resp = await browser.fetch('https://test.com/my-do/5-step/increment');
const rpcResult = await client.increment();
// 4. Confirm that results are as expected
expect(await resp.text()).toBe('11');
expect(rpcResult).toBe(12); // Notice this is a number not a string
// 5. Verify that storage is correct via RPC
expect(await client.ctx.storage.kv.get('count')).toBe(12);
});