The Signs of Failing Test Automation

Realizing these signs early might help your career.

The following signs of Failing Test Automation (end-to-end via UI) are everywhere. Realizing these signs early might help your career (position well).

· 1. Very low productivity
· 2. No signs of Continuous Testing (daily) as Regression Testing
· 3. The Team does not trust “Test Automation”
· Why do IT executives tolerate dying and totally useless “Test Automation”

1. Very low productivity

It is common and wrong for IT management to accept very low productivity on automation work. I completed several planned 3-month test automation Proof of Concept (POC) in 2 or 3 days, with high quality, of course.

The terms “In-Sprint Test Automation” and “Shift Left Testing” have become popular (at least at the talking level). This is not just completing automated testing of the user stories in the current sprint, the much more work (after the first sprint) is to keep all existing automated tests (many people did not realize this until I pointed it…