Why do Test Managers/Architects Avoid Selenium WebDriver, the Best Web Test Automation Framework?

Human weakness.

If I ask you, “A car is well-designed as Poshcue, easy to maintain as Toyota, safe as Volvo, certified by the top government authority in every country, and accelerates as Ferrari. Also, it is super easy to drive. Its price is $0. Will you buy it?” The answer, of course, is YES. Selenium WebDriver is such kind of thing in web test automation. In doubt? I recommend reading the following articles (technical factors) after this one (human factors):

• Why Selenium WebDriver is So Easy to Learn?
• Correct a Common Misconception: “Setting up Selenium is Complex and Time-Consuming” with a benchmark test.
• Playwright vs Selenium Speed Comparison
• Cypress vs Selenium WebDriver Comparison by Example
• Page Object Model is universally applicable in web test automation
• Set up, Develop Automated UI tests and Run them in a CT server on your First day at work (by my daughter)

However, in the software testing industry, crazy things happen. The senior test engineer/management often choose a much inferior test automation framework/tool, with all sorts of problems and limitation, and also a high price tag.