Automation is no longer providing value

Testim

Question: How do you know when automation is no longer providing value for your team?

Insights:

When discussing food, an expiration date is a date by which a supplier suggests you consume their product. Some foods, like dairy or meat, go bad and can cause us harm. Other foods, like tortilla chips or crackers, just get stale; they may taste OK and not kill us, but usually, we don’t enjoy stale food because part of the value we derive from food is enjoyment. When food items have an expiration date, we say they have a shelf life; the shelf life ends once this date has passed. Some of the tests that we perform release-over-release may also have a shelf life. Eventually, these tests become of so little value that they are no longer worth running, or they are not worth running frequently.

https://responsibleautomation.wordpress.com/2017/04/11/dont-eat-stale-automation/

-- Paul Grizzaffi

Insights:

When you stop maintaining or updating the automation suite while actively enhancing/ changing the product you are automating. Your automation gradually loses it's valued and eventually the dev's just skip the tests on every commit.

-- Avinash Mavireddi

Insights:

When our Automation scripts get failed due to last-minute code change before release !!

-- Ajay Lunia