Codex / AI should review CUJs and E2E test artifacts to make sure they are in sync
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 45
- Forks
- 6
- Avg merge
- 7h 14m
- Merged PRs (30d)
- 51
Description
Codex should be reviewing the E2E test artifacts (e.g. videos) and ensure they are in sync with the CUJs.
I thought I had added reviewer guidelines to AGENTS.md but I guess not.
Not sure if there is additional work we'd need to do to make the testing assets e.g. movie available to codex.
As an example
Here's a run where the movie produced shows the runner getting added in the console
https://github.com/runmedev/web/actions/runs/22084787987
https://storage.googleapis.com/runme-dev-assets/cuj-runs/runmedev-web/22084787987/1/index.html
This is an explicit step in the CUJ
At some point the movie stopped showing it
Codex should have caught that and prevented it
I think it likely got broken by
https://github.com/runmedev/web/pull/106
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the proposed reviewer guidance in AGENTS.md, then inspect the linked GitHub Actions run and its stored E2E artifact at the provided URL. Compare the movie with the corresponding CUJ, including the runner-added step, and define completion as Codex detecting and preventing this kind of mismatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100