Trying to move to QA from D is proving to be a P in the A when you happen to work for a company with no testing culture.

Back from a weeks vacation I checked the logs of the customer calls and there were complaints that a new version of a program that had been sent out was much worse than an earlier version. Another customer complaining that although he had been promised that a problem had been fixed, when he tested it the problem was still there. Full details of the problem were given in the log and I could see that a simple boundary test would have caught the bug.

I believe I have made a difference with the areas I've been involved in directly - smoke tests are always done on a new release and we are now working on unit tests. But there's still so much to be put right and that I want to change and there are times when I wonder if it is all just too much.

Which leads me to the Catch 22 - without direct test experience to put on a resume then it's hard to move on but if I stay to try and get the experience then I might not get it...

Just to make things even more confusing I did a search for testing vacancies and found one that seemed very familiar, seems my company is advertising for a tester. So what is going on and why do I have a boss that cant communicate with someone who's been bombarding him with test ideas and articles for over a year ?

Yossarian was moved very deeply by the absolute simplicity of this clause of Catch-22 and let out a respectful whistle.

 “That’s some catch, that Catch-22,” he observed.

“It’s the best there is,” Doc Daneeka agreed