Testing is hard. Maintaining tests is even harder.
When we first started using Selenium WebDriver, writing a test meant creating a one-off function that performed the given task, but duplicated a bunch of code, and used hard-coded elements if any HTML/CSS got involved. Trying to get coverage on something as large as the Behance Network (be.net) became bloated and unmaintainable.
Without an easy way to create and improve tests as features changed, QA + testing became the last priority in development.