Tweet
I NEED HELP! Anyone have experience with Software QA?
Hi all!
I am in need of REAL HELP here.
Yesterday, I was at an interview for a job at a BIG company that among other things produce software.
The job title is "Software Quality Engineer"
The primary task of someone in this job is (as I understand it) to plan and complete a QA process in the span of a product development cycle. This could take more than a year and involves testing at several levels.
The basic timeline is like other software products:
---Alpha-----Beta-----RC-----GM-> Production & shipping
Each stage is composed of several substages in which my job will be to plan and run the test that will evaluate the quality of the project sofar. Example: after several alpha releases the product should reach a stage that is fully functional, but with errors. It will go Beta at this time. Then several betas will follow to iron out all known bugs.
My problem is, that I need a better understanding of how to specify the tasks of each sub-phase.
What "mechanics" could be employed to test for bugs in software? How can I create a plan for testing this in a structured way?
I have only been schooled in project management on a basic level, but if I want to be able to do this job right (in case I get it), I will have to improve my proficiency in this area considerably. (Or I could be in REAL trouble).
If you know the answer to these questions or could help me find some litterature on the subject (Links on the net?) I will be a very happy man.
There must be at least a few of you guys out there, who have been in some way involved in Software QA.... HEEELP ME, PLEASE! :-)
Regards,
Jake
I am in need of REAL HELP here.
Yesterday, I was at an interview for a job at a BIG company that among other things produce software.
The job title is "Software Quality Engineer"
The primary task of someone in this job is (as I understand it) to plan and complete a QA process in the span of a product development cycle. This could take more than a year and involves testing at several levels.
The basic timeline is like other software products:
---Alpha-----Beta-----RC-----GM-> Production & shipping
Each stage is composed of several substages in which my job will be to plan and run the test that will evaluate the quality of the project sofar. Example: after several alpha releases the product should reach a stage that is fully functional, but with errors. It will go Beta at this time. Then several betas will follow to iron out all known bugs.
My problem is, that I need a better understanding of how to specify the tasks of each sub-phase.
What "mechanics" could be employed to test for bugs in software? How can I create a plan for testing this in a structured way?
I have only been schooled in project management on a basic level, but if I want to be able to do this job right (in case I get it), I will have to improve my proficiency in this area considerably. (Or I could be in REAL trouble).
If you know the answer to these questions or could help me find some litterature on the subject (Links on the net?) I will be a very happy man.
There must be at least a few of you guys out there, who have been in some way involved in Software QA.... HEEELP ME, PLEASE! :-)
Regards,
Jake
Comment