The bus-factor audit
Run this thought experiment: your best automation engineer resigns tomorrow. Which suites keep running? Who approves selector fixes? Where do the credentials live? If the honest answer is "it all slows to a stop," your automation is a person, not a practice. Every manager has watched this movie.
Four patterns that survive turnover
- A central element repository: selectors live in one shared place with healing history, not scattered across suites in one person's style.
- Review queues over tribal knowledge: self-healing proposes and any teammate approves, so the workflow teaches the codebase to whoever clicks approve.
- Golden suites: a named, protected set of must-pass flows that gate releases, so "what matters" is written down instead of remembered.
- Mechanical gates: scheduling and trigger APIs run the suites; humans read results. Anything that depends on someone remembering to run it will eventually not run.
The management takeaway
Tools don't fix bus factor by themselves, but the right structure makes the resilient path the easy path. Every pattern above is a built-in feature of our platform rather than a wiki page, which is exactly the point: process that lives in tooling survives; process that lives in people's heads leaves with them.