# What caused your automation run to fail? ❌

**URL:** <https://club.ministryoftesting.com/t/what-caused-your-automation-run-to-fail/72180>\
**Category:** Discussions\
**Tags:** automation, continuous-learning, mot-fcta\
**Created:** [6 December 2023 11:23 UTC](https://club.ministryoftesting.com/t/what-caused-your-automation-run-to-fail/72180 "2023-12-06T11:23:46Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![sharmon](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/sharmon/32/13962_2.png) [@sharmon](https://club.ministryoftesting.com/u/sharmon)\
**Post date:** [1 August 2024 12:54 UTC](https://club.ministryoftesting.com/t/what-caused-your-automation-run-to-fail/72180/8 "2024-08-01T12:54:23Z")

</div>

Bad business requirements. Same way business partners can introduce bugs with not the greatest business requirements, it can also cause automation to fail.

Hear me out. My test didn’t fail an assertion, and it didn’t throw an exception or crash, however, it didn’t test the correct things, it didn’t check the correct workflows. So, by all accounts it failed because it didn’t provide value or cover any _actual_ business need.

If a work request says to validate ‘X’ but the end user or stakeholder wanted ‘Y’ covered. I’d consider it a failure. At best it brought nothing of value, at worst, it brought a false sense of confidence/security around a project.

---

_[View the full topic](https://club.ministryoftesting.com/t/what-caused-your-automation-run-to-fail/72180)._