# Being bold and sharing an opinion

**URL:** <https://club.ministryoftesting.com/t/being-bold-and-sharing-an-opinion/66362>\
**Category:** Archive\
**Created:** [28 March 2023 09:54 UTC](https://club.ministryoftesting.com/t/being-bold-and-sharing-an-opinion/66362 "2023-03-28T09:54:17Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![katepaulk](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/katepaulk/32/8469_2.png) [@katepaulk](https://club.ministryoftesting.com/u/katepaulk)\
**Post date:** [29 March 2023 12:36 UTC](https://club.ministryoftesting.com/t/being-bold-and-sharing-an-opinion/66362/3 "2023-03-29T12:36:08Z")

</div>

If “all tests are green” it is either the day before deployment and anything non-critical has been paused, or the team is missing tests.

In my opinion, the primary use for permanently green tests is as regression markers - their greenness is an indicator that core function is working as expected.

If the qualifier is “all high priority tests are green” that’s acceptable. So is “all core function tests are green”.

An unqualified “all tests are green” tempts me to add a test that will always fail, just to prove that it’s not possible to have all tests green - or that it’s not worth fixing all possible problems.

---

_[View the full topic](https://club.ministryoftesting.com/t/being-bold-and-sharing-an-opinion/66362)._