I’ve worked on many teams and sometimes they have “workarounds” or “hacks” in the automation code.
When a known issue (product bug) causes test automation to fail it causes noise and pipelines to block.
A workaround is a temporary hack in the automation code to silence this noise so pipelines flow smoothly.
The problem is when the product bug is fixed people don’t usually clean up the workarounds.
I created a Wiper script that parses the code base for hacks and checks the status of the product bug in Jira.
If if finds the product bug is closed but the hack still exists it causes the pipeline to fail so it draws attention to the hack..