Tests that don't test anything come in at least two categories for me:

- test that were useless, are still useless and will always be useless

- tests that are currently useless but were used in the "wtf should i write" phase of coding (templating/TDD/ whatever you want to call it).

I'm partial towards the seconds, and i like when they're not removed, because often you understand how the API/algorithm was coded thanks to them (and its often unit tests). But ideally, both should be out of a codebase.

Cargo cult testing. Some people don't understand the point of testing so they just go thru the motions and end up with something that makes no sense.

Only needs to be management that misunderstands.

I’ve written plenty of do nothing tests in my time to be sure that management regularly got a report of tests being added.

"It passed all the tests so it must be working, it must be something you are doing wrong"