The site currently has little interactive state, so Bombadil would add cost without meaningful exploration. Revisit adoption when the site has workflows such as theme switching, interactive resume display, navigation state, or other behavior where generated action sequences can expose bugs that example tests miss.
Initial adoption should:
- Identify one high-value interactive workflow.
- Define actions and invariants rather than visual snapshots.
- Run locally and in CI.
- Preserve reproducible failing traces.
- Complement unit and Playwright tests rather than replace them.
Candidate properties include content stability across theme changes, correct theme-specific download links, repeated-action consistency, link reachability, and absence of horizontal overflow.
Bombadil: https://github.com/antithesishq/bombadil
The site currently has little interactive state, so Bombadil would add cost without meaningful exploration. Revisit adoption when the site has workflows such as theme switching, interactive resume display, navigation state, or other behavior where generated action sequences can expose bugs that example tests miss.
Initial adoption should:
Candidate properties include content stability across theme changes, correct theme-specific download links, repeated-action consistency, link reachability, and absence of horizontal overflow.
Bombadil: https://github.com/antithesishq/bombadil