It all boils down to a cost/benefit equation, and Public Relations/Human Resources politics.
1. Cost/benefit
It is Management's job to ponder: How much does it cost to perform QA after programmers deliver? Also, how thorough should QA be? Meaning how deep, how long, how many people and resources involved?
Against this: How much revenue does the company actually lose from disgruntled clients?
2. PR
Enter the Public Relations people. PR main functions are to publicize products and services, and to take the heat off the company (and Management) when said products and services fail - as they are bound to do when QA is poor or inexistent.
Unless we are talking monopoly - in which case client opinion won't be worth a peace treaty in the Middle East - PR will take pulse and temperature of client reaction and pass it on to Management. The Powers That Be can then react and say ok, we chose this path, or unleash their wrath upon lesser beings.
3.HR
Enter HR politics and mores. I'm not talking here strictly about the Human Resources Dept people, who are no more than dummies in the way between Employees and Management (kind of an internal PR, trying to sell Management BS and at the same time avoid upper echelons disembowelment at the hands of the company's little people).
Actually, I'm talking about the interaction between bosses and bossed, dictated mostly by both their personalities and the country's Unions strength.
Employee (programmer in this case) incinerating will be an option for the weak minded manager who is actually responsible for the lack of QA.
The fact is, when shit hits the fan, it will spread around, but most of it will go downwards. Gravity, you know.
If this is your case, it's just the reality dealt to you by Chance, Fate, Karma, you name it. What to do?
* Kill your boss, take his place and order proper QAs. Not recommended. Even if CSI didn't catch up with you, you'll probably go to all that trouble just to look up and find another boss-of-you who won't sign for the money you'll need to QA properly (there, I just coined a verb)
* Talk your boss into it. Improbable. If he is not a moron, his decision will have solid foundations and you won't be able to shake them. And if he is a moron, he won't listen to reason. A reasonable moron is an oxymoron...
* If you have a strong character, or a strong Union, or both, stop your boss in his track reminding him it was not your decission or responsiblity.
* Try another company. You probably will, anyway, if you try the one above. If you are lucky, you might find the odd company who really cares about customer and programmer happiness.
* As you said, abandon all hope and choose another, more rewarding, career. Avoid dope dealing, though. Trying the stuff before delivering is frowned upon.
Good luck.