This document discusses several anti-patterns that are commonly seen in automated testing practices. It identifies anti-patterns such as relying primarily on UI tests, using screen recorders to build tests, ignoring intermittent low priority bugs, having all tests run as a monolith test suite, having testers write automated tests instead of developers, and thinking that achieving 100% test coverage equals high quality tests. For each anti-pattern, it provides examples of why they look like good solutions on the surface but introduce problems related to maintenance, fragility, dependencies, ownership, and not actually guaranteeing test quality.