What you should avoid doing in your Selenium project

When you have time, you should read the documentation from the Selenium official site as there are many useful things to learn from it.

One of the sections of the documentation is about the discouraged test practices. In other words, things that you should not do in your projects.

For example,

• you should not try to automate CAPTCHA (because it is impossible; instead, ask the dev team to disable it in the test environment or add a URL parameter that enables/disables it)

• logging in to GMAIL (not a good idea as it is against GMAIL usage terms so your account may be closed; this is also slow and unreliable)

• you should not have dependent tests (your tests should run in any order)

• you should not use Selenium tests for performance testing (because Selenium tests are slow and you need fast tests in performance testing; use JMETER instead)

• you should not use Selenium tests for link spidering; use specialized libraries for this

• you should to automate 2 factor authentication

I would add one more discouraged practice:

• do not implement visual testing (testing of the look and feel of the UI) in Selenium

Read more here.