e2e test

Backlinks

practice - ad hoc browser use

So, not part of e2e tests, like Playwright, but rather like the browser use MCP or the browser use built-in to Codex for doing ad hoc testing of new features.

see in context
practice - automated QA

This also seems like a good idea, but I have not done it: agent-generated artifact for human review -- multi-step QA plan. Instead I've preferred to put more and more emphasis on the e2e tests, and to do minimal QA-ing.

see in context
practice - custom review tooling

I've created a change review app powered by e2e tests. It creates scenario artifacts that are synchronized with the video of the E2E test. The artifact includes the test code (show below), which is synced with the video. It also includes all the data about what is stored on the filesystem, in cloud stateful storage, and in S3. All of it is time travelable.

see in context
practice - handoff to cloud agents

I haven't done this, at all. I do have CI run some standard tests when I push, but it doesn't even run the e2e tests.

see in context