Are you paid to care about "finding millions of real user passwords in the test database"? About caring how or whether your code is organized? About what should be happening in a unit test?
If you are paid to care about it, absolutely do so because that's your job. If you aren't, though, at most you should inform someone who is paid to care about it and then forget about it because it's not your concern.
Life is short and there is only so many waking hours in a day, so we need to budget them accordingly. If you can't bring yourself to be less passionate about your work even though you realize it's actually causing you and your coworkers problems, perhaps it's a sign you need to change professions entirely.
Their actions, though, say that they want someone who hustles and creates bugs and then puts on a good show fixing the bugs they themselves created.
Saying it like that, I guess the solution is to just get out, but it's hard to accept "just find another job" as the solution when I'm not even employed right now.
> Are you paid to care about "finding millions of real user passwords in the test database"?
...are never clearly answered, in 99% of all jobs everywhere.