Say exactly what you mean, then I'll let you know if I take offense.
I wonder, did you look for a way to move testing from people into easy test cases (and failed) or you just don't need it? After all, you don't do the hard testing work. No offense.
You test everything you can,
but you don't have the luxury of spending countless
hours writing test routines because your working
on 2 other programs, making database modifications,
generating documentation and attending meetings
(where you get assigned additional work to do).
While all this is going on, that program you wrote 2 years
ago stopped working due to an environment change
or security update, so now you also have a ticket/work order.
At this point your manager starts leaning on you about the original
program your testing because the users (that you didn't involve)
complained to their manager (due to the delayed release) who in turn
talked to the CFO and so on downhill to me.
Until your in a situation like this, I don't think you can
understand... school is not the workplace.
I involve my users, everything works better that way.
Forgot to mention the normal financial application changes
which have to be written in LDL+ a Unisys bastardized cobol