Some Important Testing Questions

쥔장이 구독하는 메일링 리스트에는 가끔 귀한 주제들이 언급된다. 아래 내용도 그냥 지나치기 쉬운 얘기이면서도 반드시 짚고 넣어가야 하는 이슈인 듯 하다.

1. How will you make sure the Test Cases made are complete or not.

Ex: U had made  Test Case for Login Page. How will you make sure that you had covered all test Scenarios etc.

Always you will write test cases based on some requirement documents, Once if you covered all the requirements its test case complete. you can find the missing requirements by mapping the test cases with requirements in Traceability Matrix document.

2. How you can use Use Cases for making test Cases

In Use case there will be functional points, In which you can derive the senarios and write test cases

3. After doing regression testing, which test cases will u cover. Whats the procedure

As per my knowledge you need to perform the Acceptance testing

4. If you are handling a team and theer are conflicts in your team, how will you remove them or what steps would you follow

You can answer like as I am a gud lead, I ll never allow to create a conflict. Because good lead will always give a follow up to the whole team, Then onely he can find the productivity. if you find any, then you have to find the root cause for the conflict. then you can warn the bee for the cause. At final step you can move the minority members in to another project.

5. If you had done any payment in a website , a message occurs "Processing ...." How will you test that particular page.

Before making payment just ensure that the website is security tested and certified by some trusted bodies. Without that you shouls not make any payment.

6. Have you done any type of reviwes. What you do in that. Whats  the process

Basically review is a verification method in which you can discuss any thing and finding loop holes. for example in requirement review you have to walkthrough the requirement and find the missing requirements. Its called requirement bug. Reviewing is having many steps like Organising, scheduling, conducting, collecting feedback, discussing defects. But remember one thing you have to read the documents and the writer in the review committee should mark the review members feedback. you should not  let the people argue, then it will never end.

7. How will u make sure that there are no duplicate bugs logged in bugzilla.

 

As per my knowledge there is no separate way to find the duplicate bug, before logging the defect you can search in the bug list with the key word that any other bug is already having the same keyword. then you can open and verify the bug