hi , i had an interview for a qa and got stuck up in the very first question..Although i have the answer i could not put it in words , can someone help me .. The question was very basic " Tell me your role as a qa from the beginning of the project, how you choose whether to automate or test manually and till you complete testing the application? he was expecting like the all process of qa testing . can someone help me as i have another interview
Total Answers and Comments: 7
Last Update: September 03, 2007 Asked by: dave1969
RE: hi , i had an interview for a qa and got stuck up ...
I am Tester with 6 years of Experienced in Testing. I used to face this question
1) Describe your profile in your organization Initially I thought I was able to answer online But it is difficult.Write down in paper the questions they ask and the answers to it. So Hope this will help u.
This help me a lot.
My role is
1.Writing Test Plans and Test Cases
2. Distribution of work among the Junior Team Members.
3. Follow up with team regarding the work
4. Giving Trainng to Freshers on WorkFlow Management
5. Maintaing documnets for Audit
6. Giving the input Data for Estimation of the Project
RE: hi , i had an interview for a qa and got stuck up ...
Its quite casual question. Because the answer to this question gives the interviewer clear picture of your expertise in QA and he many need not go for any further questions and waste his time.I will try to answer your question in the following way.QA is a crucial role in any project as he is involved right from the first phase of the project. Suppose let us consider we have received a project proposal from client.1. In the first stage (requirement stage)--> we collect the requirements from the customer/client and will have a review to check the achievablilty. For this high level QA related personnel will be involved (SQA Analyst or SQA Manager)2. Once SRS/FRS is prepared --> that is to be reviewed parellely by a QA Manager to check if we are in position to handle the execution w.r.t given schedule and resources. QA Analyst start preparing system test cases here.3. One SRS is converted in to Design documents (HLD and LLD) again we will be having a sort of review by QA Analyst/Architect to check if the design is optimum and as per the standards. QA person start preparing Integrations level test cases here.4. Once design is put in to implementation--> QA person will be involved in review and unit level testing.5. Once all the modules/units are coded development start with integrating all those units to make a single unit. Again QA person will be testing here using Integration Test Cases that he has already prepared in step3.6. Once the integration is done QA people use System level test cases to test the system behaviour. At the same time he will be preparing the Req Traceability matrix to check if all the given requirements are transformed in to test cases at the end.7. Once the complete system is deployed in offshore test server-- QA person conduct different types of testing to check the functionality of the application...eg: Pre deployment testing etcAs depicted above QA Analyst will be involved in almost all stages of the PDC.If you are applying for any managerial level you can stressmore on the first three points.If you are applying for any junior level you exclude first two points...All the best--Vijay Sarvepalli
RE: hi , i had an interview for a qa and got stuck up ...
This is a very standard question in the interview. Anyone who is going for an interview as a QA Tester has know the answer.
The situation that you have mentioned (eventhough I know I cannot express) has happened to me many times. Therefore I started practising myself day and night. There is no way out except practice with a voice out.
The ways that you can practice I have given in
http://www.qaquestions.com
If you read those questions by heart I am sure you will succeed.
RE: hi , i had an interview for a qa and got stuck up ...
You can tell the 11 Step V model it will helpful at the time of interview 1. Test the software requirements 2. Assess the development plan and status 3. Develop the test plan 4. Test the software design 5. Programe phase execution 6. Execute test & Record resutls 7. Report resutls 8. Software installation 9. Acceptance testing 10. Test for software change 11. Evaluating the testing process
