interview question

Replies to This Discussion

Permalink Reply by Samrat Jha. on October 31, 2011 at 11:46am

 

 Simple yaar.. Traceability Matrix will serve your purpose ...  !    as far as writing test cases are converned .. We do not write test cases for every functionality ..   Your test plan tells you that for which functionality you need to write test cases and for which functionality you need not to... ! 

 Still have confusion ..? do let me know....

 

Samrat Jha

• ▶ Reply

Permalink Reply by Pvarun on October 31, 2011 at 3:25pm

If we dont have time.... we will cover the major part of the funtionalty is working fine or not.. Your test plan tells you that for which functionality you need to write test cases and for which functionality you need not to...

• ▶ Reply

Permalink Reply by abid on October 31, 2011 at 3:26pm

first   option is that  u should talk your T/L or Pm in this situation .What they suggest 

 Second option is that If u do not have time to write test cases .test functionality first after that u have time then write test cases .testing functionality is more important than writing test cases

Second  option is that  u should talk your T/L or Pm in this situation .

Through tracebitly  matrix .

It is mapping between test cases and requirement.

• ▶ Reply

Permalink Reply by Balaji on October 31, 2011 at 3:30pm

 

 

Yes, What all said is correct and please give importance to sanity, adhoc and exploratory testing..... Experience based technique with error guessing

 

Regards,

Balaji

• ▶ Reply

Permalink Reply by abid on November 1, 2011 at 10:44am

Sanity testing: when tester receive  build for testing.If there is minor changes in code .tester perform cursoury reg ration or narrow reg ration testing .to check that build is enough for testing or not.

In sanity we perform not full reg ration testing but also narrow reg ration that the build is enough for in a sane condition or not. .

Adhoc testing: if there is not enough time for writing test cases tester perform adhoc testing. For adhoc testing condition is that tester should aware such type of application previously. On the basis of knowledge and experience of prior such type of project tested tester test that application.

Exploratory testing: tester is not aware that type of application which is going to test. perform exploratory testing. In this type of testing tester learn while testing.

• ▶ Reply

Permalink Reply by Behbood Hussain on November 1, 2011 at 8:31pm

In such cases, one thing needs to be clear: You cannot test everything! I would adopt a risk-based testing approach where I would spend a couple of hours with the BA's and developers and come to an agreement on the functionalities that are critical to the end-user (that have not been covered as part of existing test cases) when the application goes live into production. This would help me determine the areas that I need to test. 

 

Of course, you need to ensure that all stakeholders are on board with this approach and are willing to accept the risk. 

 

This is perhaps the most logical way to handling a situation of this nature.

• ▶ Reply

Permalink Reply by Balaji on November 3, 2011 at 2:12pm

Yeah.., its right... Some thing similar to walkthrough

• ▶ Reply