Advertisement
Hi there,
So I'm taking a break from school (majoring in econ and computer science) to do some stuff in the real world. I'm applying for junior QA positions but I really don't have much of a clue. What kind of stuff should I know? To be more specific, in your opinion what are the top 5 skills that a badass QA engineer has and how should I go about getting them?
In addition, what are some good websites and books that I should check out?
thanks
So I'm taking a break from school (majoring in econ and computer science) to do some stuff in the real world. I'm applying for junior QA positions but I really don't have much of a clue. What kind of stuff should I know? To be more specific, in your opinion what are the top 5 skills that a badass QA engineer has and how should I go about getting them?
In addition, what are some good websites and books that I should check out?
thanks
Advertisement
Advertisement
-
Re: What should I know to be a QA?
Mon, January 17, 2005 - 2:27 AMOne other thing, What Certifications should I get? -
-
Re: What should I know to be a QA?
Fri, January 21, 2005 - 12:54 PMYou probably should go back to school and complete your degree. -
-
Re: What should I know to be a QA?
Sun, January 23, 2005 - 9:28 PMnot in the cards until (at the earliest) september. Really I'm looking for any interesting tech work that wont crush my soul. thoughts? -
-
Re: What should I know to be a QA?
Fri, February 4, 2005 - 11:27 AMall tech work will ultimately crush your soul ...
On the qa side:
I'm not in QA, but I build tools for them, so this is all some sort of BS ...
finish your degree, a lot of place won't even consider you without one, unless
you can point to some amazing piece of work. The alternative is going in as a manual tester (and the bone crushing boredom that goes with that ), and then hope you can move up .
QA people are a strange breed, you need a mentality that enjoys breaking things,
tends to understanding the big picture (how does this thing I'm testing
fit into the picture, how would a customer use it)
Be familiar with a scripting language: Perl/Python/TCL, The better you are
with this, the more valuable you will be.
You need to understand the software development cycle, practical experience
in this area is much preferred to the theoretical (play around with an open source project to get that experience)
Understand how a bug tracking system works - look at bugzilla.
Basic system admin skills will take you a long way, chosse your favourite
platform and understand everything about it.
Understand a unit test framework, perl has one built in, Junit, CPPunit are out
there too.
-
-
-