Today I got lectured by one of our Seniors that my automated test isn't useful because it always fails. Reminded him that it only fails because of a bug that's assigned to his team for four months now. He answered that I should remove the test case. Sometimes I honestly question why they even have a QA if they ignore at least 80% of reported bugs...

Your senior is a bad dev, if it fails due to a bug it should be fixed.

Some times I can flag a test as ignore if we know it will take time to fix since ignored tests are listed as ignored when we run.

And in our case, faild tests get emaild to all devs if we commit them since we have automatic build and test.

@Voxera That's pretty much what we're trying to implement. The Error isn't a big one (input gets marked as erroneous even though it isn't) and theoretically the product can be used in its current condition (which is the reason the bug always gets postponed, I assume) but I will not ignore shit if I do not get the okay from the whole CI team. A year ago, when it wasn't their problem, they wanted every little piece automatically tested, now that I worked through 16 frickin years of "naturally grown" code that was never intended to be tested by a machine they want me to throw the test list out of the window because they can't keep the damned thing from adding a class to a fucking field? Horrendous payment, okay, being the guy who does "only" some test scripts, I can live with it but butchering my baby for their inability to fix a almost half a year old ticket? Oh hell no.
P. S. I might have vented a little bit too much towards the end, sorry for getting off topic.

@Godisalie get it off your chest dude, you are committing to your task and job.