It's internal development (Portugal) developing something for an internal department (Germany). There's nothing professional going on here so we are far from any ci/cd pipeline. One person can change everything, because it's just two developers (1 frontend, 1 backend).
Plus things are busy and we (team in Germany) are way more interested in this thing working well than they (team in Portugal) are since they have higher priority tasks..
Of course I can say fuck it and live with the poor quality caused by circumstances that were partially caused by poor management decisions of the company but I'm not able to care little enough.
If you have tests you have to automate them and have a pipeline which stops any deployments when these tests fail.
You definitely have a mindset issue and not a management or tool issue.
I am not sorry but as a DevOps Engineer I can only say you guys are a lousy hack and should probably seek a different job.
the real question is why doesn't the CI/CD prevent merging with failing tests in the first place. i have not worked in any company that allowed that for at least 15 years.
Rn I'm in a project where everyone that has access to the code is given the role of owner of the group so we have permissions to skip any and all measures since owners don't care.
I'm so happy that tomorrow is my last day. So happy.
Proper procedure would have been the dev updating the uts so that they pass. If all they updated was adding ignore or commenting out code in the ut, even better!