Return to Answer

Anti-patterns in Test Automation

1. Using implicit waits
2. Using Recorded playback
3. Using brittle, layout based selectors
4. Not isolating test data between tests
5. Not consistently using Page Objects
6. Tests that only have negative assertions
7. Using assertions mid-way through a test
8. Repeating parts of tests due to the same setup
9. Not considering the Sad path of user entering invalid data
10. Forcing all tests to go through all pages in complex workflows
11. Assuming that test automation cover accessibility and usability
12. Using cryptic names and acronyms in test and suite descriptions
13. Not considering optional workflows for both happy and sad flows
14. Only testing 1 browser and assuming that other browsers work fine
15. Not using Page Helpers to DRY up and name common code sections
16. Using general assertions like have_css over specific ones like have_button
17. Bullet Points that gradually get longer as you scan your eyes down the full page

I would say that I've made every mistake in this list when starting out, before I knew better so I think they all meet your criteria of 'seemed ok initially'

Anti-patterns in Test Automation

1. Using implicit waits
2. Using Recorded playback
3. Using brittle, layout based selectors
4. Not isolating test data between tests
5. Not consistently using Page Objects
6. Tests that only have negative assertions
7. Using assertions mid-way through a test
8. Repeating parts of tests due to the same setup
9. Not considering the Sad path of user entering invalid data
10. Forcing all tests to go through all pages in complex workflows
11. Assuming that test automation cover accessibility and usability
12. Using cryptic names and acronyms in test and suite descriptions
13. Not considering optional workflows for both happy and sad flows
14. Only testing 1 browser and assuming that other browsers work fine
15. Not using Page Helpers to DRY up and name common code sections
16. Using general assertions like have_css over declarative ones like have_button
17. Using authenticate / authorization in multiple tests leading to massive test failures
18. Bullet Points that gradually get longer as you scan your eyes down the full page of them

I would say that I've made every mistake in this list when starting out, before I knew better so I think they all meet your criteria of 'seemed ok initially'

Anti-patterns in Test Automation

1. Using implicit waits
2. Using Recorded playback
3. Using brittle, layout based selectors
4. Not isolating test data between tests
5. Not consistently using Page Objects
6. Tests that only have negative assertions
7. Using assertions mid-way through a test
8. Repeating parts of tests due to the same setup
9. Not considering the Sad path of user entering invalid data
10. Forcing all tests to go through all pages in complex workflows
11. Assuming that test automation cover accessibility and usability
12. Using cryptic names and acronyms in test and suite descriptions
13. Not considering optional workflows for both happy and sad flows
14. Only testing 1 browser and assuming that other browsers work fine
15. Not using Page Helpers to DRY up and name common code sections
16. Using general assertions like have_css over specific ones like have_button
17. Bullet Points that gradually get longer as you scan your eyes down the full page

Anti-patterns in Test Automation

1. Using implicit waits
2. Using Recorded playback
3. Using brittle, layout based selectors
4. Not isolating test data between tests
5. Not consistently using Page Objects
6. Tests that only have negative assertions
7. Using assertions mid-way through a test
8. Repeating parts of tests due to the same setup
9. Not considering the Sad path of user entering invalid data
10. Forcing all tests to go through all pages in complex workflows
11. Assuming that test automation cover accessibility and usability
12. Using cryptic names and acronyms in test and suite descriptions
13. Not considering optional workflows for both happy and sad flows
14. Only testing 1 browser and assuming that other browsers work fine
15. Not using Page Helpers to DRY up and name common code sections
16. Using general assertions like have_css over specific ones like have_button
17. Bullet Points that gradually get longer as you scan your eyes down the full page

I would say that I've made every mistake in this list when starting out, before I knew better so I think they all meet your criteria of 'seemed ok initially'

Anti-patterns in Test Automation

1. Using implicit waits
2. Using brittle, layout based selectors
3. Not isolating test data between tests
4. Not consistently using Page Objects
5. Using assertions mid-way through a test
6. Repeating parts of tests due to the same setup
7. Not considering the Sad path of user entering invalid data
8. Forcing all tests to go through all pages in complex workflows
9. Assuming that test automation cover accessibility and usability
10. Using cryptic names and acronyms in test and suite descriptions
11. Not considering optional workflows for both happy and sad flows
12. Only testing 1 browser and assuming that other browsers work fine
13. Not using Page Helpers to DRY up and name common code sections
14. Bullet Points that gradually get longer as you scan your eyes down the page

Anti-patterns in Test Automation

1. Using implicit waits
2. Using Recorded playback
3. Using brittle, layout based selectors
4. Not isolating test data between tests
5. Not consistently using Page Objects
6. Tests that only have negative assertions
7. Using assertions mid-way through a test
8. Repeating parts of tests due to the same setup
9. Not considering the Sad path of user entering invalid data
10. Forcing all tests to go through all pages in complex workflows
11. Assuming that test automation cover accessibility and usability
12. Using cryptic names and acronyms in test and suite descriptions
13. Not considering optional workflows for both happy and sad flows
14. Only testing 1 browser and assuming that other browsers work fine
15. Not using Page Helpers to DRY up and name common code sections
16. Using general assertions like have_css over specific ones like have_button
17. Bullet Points that gradually get longer as you scan your eyes down the full page