View Single Post
Old 08-09-2009, 03:23 PM   #20
purl4peace
Mommy of Many Interests
purl4peace will become famous soon enoughpurl4peace will become famous soon enoughpurl4peace will become famous soon enoughpurl4peace will become famous soon enoughpurl4peace will become famous soon enoughpurl4peace will become famous soon enough
 
purl4peace's Avatar
 
Posts: 139
Karma: 660
Join Date: Sep 2008
Location: Wake Forest, NC
Device: Kindle DX, Sony PRS-505, Cybook Gen3
Quote:
Originally Posted by pilotbob View Post
I'm not sure what you did back then. But alot of QA (testing) these days is done by developers... especially on embedded and low level systems. It is extreemly challenging and technical. It usually involves development skills as well as trouble shooting and very good communications skills.

Many people see QA as "entry level", a bunch of monkeys banging on a keyboard of some business app trying to make it fail. But, a good QA person knows how to plan a test, write test plans, define boundary testing, define surface area for security attacks, and then write code to automate it all including controlling the environment etc. QA can be a very technical and challenging job.

BOb
Amen BOb,

Most QA is moving towards automated testing which, depending on the tool requires a knowledge of PERL, UNIX shell scripting, Java, VB, SQL, JCL and/or C.

My last job was working for Satan, er, a major healthcare insurance company working on validating their Claim Book of Record. I had to learn Mainframe tools, SQL, JCL and write macros that would do textfile comparisons (without worrying about "false positives" due to dates, white space etc).
purl4peace is offline   Reply With Quote