58 signs that you are still bad at Selenium test automation

Photo by Anders Jildén on Unsplash

If your Selenium automation code does any of following, chances are good that your projects need serious changes.

The following items are not listed in a specific order.

SELENIUM TESTS

1. Tests are dependent on each other
2. Tests work only on a specific environment (test) and not on all environments (dev, staging)
3. Tests work only on Windows and not in Linux
4. Tests can be executed sequentially but not in parallel
5. Tests run in virtual machines but not in docker containers
6. Tests read sensitive information from property files instead of environment variables
7. Tests work on a single browser and not on all major browsers
8. Tests work on a specific language only (English but not French or Spanish, if the site supports multiple languages)
9. Tests work only in headed mode, not headless
10. Tests use Selenium classes, methods and objects
11. Tests use hard-coded test data that is valid for a single environment
12. Tests have more than 1 purpose
13. Tests have more than 20 lines of code