README
¶
fakegithub
The in-process GitHub fake from internal/github, served on a loopback port so
that a browser can reach it.
The Playwright suite drives the real binary, and every layer below the browser runs against that fake as a test server. A browser cannot reach a test server that lives in another process, so connecting an App, verifying it and watching a runner appear were tested everywhere except the page they happen on. This is the same fake with a port.
It is a test-only program. It mints nothing, verifies no signature and answers every App as though its credentials were perfect, which is what makes it safe to point a browser at and useless for anything else.
Running it
You rarely start it yourself. The connect Playwright project starts it through
web/tests/support/serve-connect.mjs (go run ./test/fakegithub) and reads the
line it prints:
fakegithub url=http://127.0.0.1:PORT app_id=N installation_id=N
To look at it by hand, run go run ./test/fakegithub, give an installation that
URL, and stop it with Ctrl-C. It serves three repositories (acme/widgets,
acme/site, acme/infra), the same names the demo seed uses.
Documentation
¶
Overview ¶
Command fakegithub serves the in-process GitHub fake on a loopback port, so that a browser can reach it.
The Playwright suite drives the real binary, and everything below the browser already runs against `internal/github`'s fake -- but that fake is an in-process test server, so the one client that could never reach it was the one an operator uses. Connecting an App, verifying it, and watching a runner appear were therefore tested at every layer except the page they happen on.
This is that fake with a port. It is a test-only program: it mints nothing, verifies no signature, and answers every App as though the credentials were perfect, which is exactly what makes it useless to anything but a test and safe to point a browser at.
Source Files