Why are unit tests behaving like e2e tests?

[dominictobias-bullish]

Following this guide: https://elysiajs.com/eden/test

The test fails unless I have an actual API server running in another terminal. Importing app or typeof App from the server entry does not work.

What am I missing here?

import { beforeEach, describe, expect, it, spyOn } from 'bun:test'
import { edenTreaty } from '@elysiajs/eden'

import * as articleImports from 'src/routes/article'
import { type App } from 'src/index'

const getArticleSpy = spyOn(articleImports, 'getArticle')

const api = edenTreaty<App>('http://localhost:9420')

describe('News Article', () => {
  beforeEach(() => {
    getArticleSpy.mockClear()
  })

  it('matches snapshot', async () => {
    getArticleSpy.mockReturnValue(
      Promise.resolve(sampleArticle as Article),
    )

    const { data } = await api.article['*'].get()

    expect(data).toMatchSnapshot()
  })
})

bun test v1.0.30 (1424a196)

src/routes/__tests__/index.test.ts:
ConnectionRefused: Unable to connect. Is the computer able to access the url?
 path: "http://localhost:9420/article/*"
✗ News Article > matches snapshot [2.74ms]

 1 pass
 1 fail
 1 expect() calls
Ran 2 tests across 2 files. [19.00ms]

Connection is refused unless the server is running for real in another terminal.

[dominictobias-bullish]

I had to use app directly rather than edenTreaty. The docs make it sound like they are equivalent but with type safety, but one is unit testable and the other is e2e testing.