I am a Business Systems Analyst - more specifically the only QA Test Planner on 2 agile dev teams. One of the teams is great, we write tests, find bugs, fix them with the help of our WONDERFUL developers...the other team, doesn't like to test, doesn't like to write business requirements, they don't like find defects, and they place all the blame of defects on me! Well if you never tested it, how did you know that it worked? The developers are on that team are good, but apparently nothing they code can be 'unit tested' it all must be front-end tested.
"It is cheaper to fix in developement then once it is in Production"
(Context: I work in academia. Not two weeks ago a grad student admitted he had no test suite for his project, but it was okay because he "ran a few jobs and made sure the output looked okay" whenever he changed something.
Last week a post-doc suggested that we upgrade our server because the post-doc's code has a memory leak that was crowding out other services. [Admittedly, this is also because Jetty is not resilient to hosting badly-behaving code.]
I have had to tell a professor "'Do what I mean' is not a spec." [I also had to persuade them that record storage in xml files had substantial disadvantages compared to a datatabase.])
I am sorry for bs Analyst's but glad that at least one of my teams is amazing! I love testing with them. I know ALL about 'the cheapest' tester's...I trained my replacement in my last job that who was a contractor in India. More than 6 mo. later she contacted me asking for help debugging a test...the component was named 'Prior to 2011 SQL Validation' I was on the phone trying to explain. I totally told my old manager since I should not have even picked up the phone when she called!