Anti-Patterns in Test Automation

While you’re building test automation frameworks, these pitfalls can take the magic out of your efforts. Beware of those

  1. HardCoded Test Data
  2. HardCoded Environment and Configuration
  3. Conditional Assertion
  4. Assertions without traces
  5. Test jumbled with Business logic

Do you agree or disagree with some of the anti-patterns discussed above? Are there any others that you have seen that could be dangerous to a project?

1 Like