** Runs after each Tinderbox or candidate build to quickly find full-stack bugs
** Scope, depth, and maintenance is owned by QA
** Tests can be created after area is delivered and UI is stable enough to make cost acceptable
** Must be sheriffed by QA, via a combination of alerts and result reviews
** Primarily runs on-device to test full stack