srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• May 2nd, 2007

 

If the customer changing the reqs ...  : If the change came in between the testing time of previous requirement ( change) then i can stop testing and intimated to my TL... if the change came after completion testing of prev change then i can go for testing .. I think in this situation we can't do anything like reporting to PM or any except doing testing for new changes..  at present we doing like this only..  coz all the risk analysis, cost estimations are already done by PM and given it for testing..

Suppose you have....  :  In between we can review test cases ( by me or peer)..  try to prepare effective test cases , or can test application upto completion part if possible...

How you know.....   : 1. Daily we check the BTS for bug status
 
2. Actually we sent a mail with bugs to concerned developers to fixed, he revert back   with status of bugs, then we can go for re testing.

3.If using any test management tool, if automatic email configuration is configured then concerned tester should receive a conformance email that the bug is fixed...

mithr17

 Profile Answers by mithr17 

• Oct 31st, 2011

 

Welcome to Agile testing!

/sorry you are throwing different things into the mix - test cases, bugs. Can you be more elaborate and clear so that other people who are interested in knowing the question and answers can understand things clearly.

Oksana

• Sep 5th, 2014

 

I will say the customer that it would too expensive for him if he would still change the requirements))

anj0506

 Profile Answers by anj0506 

• Nov 6th, 2014

 

When lot of changes in requirement is asked by client, then I will escalate this issue with team lead and will make sure that we get a signed off of the final requirement enhancement as frequent changes in requirement is affecting all documents like Test scenario, Test plans, Bug Reports; until then I will test rest of the module /part of application.

1.I will make traceability matrix for the test cases so far developed to ensure maximum coverage.

I will make sure that Test environment is ready when build will come.

2.I will review the test cases prepared by me and colleague.

For knowing the status of bug will check the status of bug (which has to be changed as processed from new to fixed).

Gaurav.khurana

 Profile Answers by Gaurav.khurana 

• Apr 18th, 2015

 

I will try to focus on that part of the requirements which are more stable.

And in these situations if test case are already written and continuously client is changing requirements instead of updating all the TC will wait and update only during execution so that it can save time and we have the final one at the time of execution.

By checking the status of the bug we can know whether its fixed or not and can confirm the same by retesting the scenario which was reported in bug

vasudha

• Apr 21st, 2015

 

The information at. The top of the file is XML namespace

narendra

• Sep 30th, 2015

 

As per Project is concerned, we are working for customers and their requirements to be met... so in this case I hope every tester must be flexible at any moment and accept the change at any time...
and if I complete my test cases writing and have some time before I receive the sprint for testing meanwhile I will review my cases with my peers and also have a glance on similar projects which were done earlier and try to identify critical areas which were aroused in such project and prepare a contingency cases as per my project is concerned.