Author @boyuan_chen argues that a spreadsheet containing user story, expected behavior, bug log, fix, and retest becomes a control surface that enables Codex to test the entire product rather than individual tickets. The post cites Greg Brockman (@gdb) and a linked demo of using Codex to test every feature in an app.
Author @boyuan_chen lists a QA workflow: user story, expected behavior, bug log, fix, retest — all captured in a spreadsheet used as the 'control surface'.
QA gets weirdly executable here.
User story, expected behavior, bug log, fix, retest. The spreadsheet is the control surface that lets Codex work across the whole product instead of one ticket.
Greg Brockman (@gdb)
codex for testing every single feature in your app:
— https://nitter.net/gdb/status/2068761809318990054#m