saransh.kanaujia

 Profile Answers by saransh.kanaujia 

• Mar 17th, 2008

 

if requirment is changing day by day then need is to check first changes made according to the requirment and is they effecting any other link it's retesting.

G.D.S.Prasad

 Profile Answers by G.D.S.Prasad Questions by G.D.S.Prasad

• Apr 15th, 2008

 

First test the new functionality added and then do regression testing.

rajeshwarash

 Profile Answers by rajeshwarash Questions by rajeshwarash

• May 17th, 2008

 

The actual test execution starts only after the software build is ready.So it doesnt effect the testing strategy.

If the reqirements are on installment basis the developers follow the evolutionary model in SDLC.

If tht situation happens during testing i will follow the below method.

I will retest added features first and then i will do regression testing on the tests on previouslu passed tests r passed this time or not?To make sure the new feature does not leads to side effects.
Then i will continue on remaining testing.

I think this will clarify u r answer.

saurabh_saxena1

 Profile Answers by saurabh_saxena1 

• Aug 25th, 2008

 

The best way to test such products where requirements keep on changing on a daily basis is to conduct testing in following way...

1. Test the latest features implemented.
2. Test them in close vicinity of developers.
3. If possible arrange as many as possible walkthroughs including dev team in loop.
4. Once latest implemented features are well tested.
5. Perform Regression Testing. (Here uyour automated regression scripts will some into great use)

-- Saurabh Saxena

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Feb 12th, 2009

 

Me working exactly for this type of project now, find the steps below how we r done testing.

-> First test the new requirement change?on the new build, if at all any issues post and report
-> Again retest all those and closed if they are really fixed
-> Next search for the impacts due to new C R for any other areas , if at all any impacts send again
-> Conducting a full round of regression testing
-> Verify the same CR will effect for any other clients...

Srinivas

vk1978

 Profile Answers by vk1978 Questions by vk1978

• Feb 22nd, 2009

 

I worked with a product testing team where every member of the team are responsible for 1 or 2
products, I as assigned one product, in that product testing client requested changes in
which few are informed well in advance and few are during the release time but not daily basis, the changed
information (documents) were provided to me by seniors and after reviewing those
changes, I attending review meetings with client and high level management for better understanding of the functionality and for all the misunderstanding that
I had were given clarification of those new changes by them, and I was ask to give information like the No of Test cases that are going to update, delete, or adding new if any
and  the issues that were raised with respect to the existing requirement and the time needed to do these tasks. so based on the information provided by me, team lead has done impact analysis and
give me the task to complete with in a specified period of time and during the release time where
I need to complete with in a day my team lead asked 2 other team members to assist me on that day, that how the thing were happened, and coming to execution of those new changes, that functionality was tested by installing on a temp server and after making sure everything is fine, I/we send a request to include the new functionality in to the main application, and on new build we again test those changed functionality and afterwards I/we executed testcases with respect to issues/defects and later execute remaining testcases.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 8th, 2009

 

I respectfully disagree with anyone who states this situation "doesn't effect test strategy."  In fact, it would cause me to revise our test strategy.  The only way these circumstances would not impact test strategy would be if they had been anticipated and processes were set in place to accommodate them. I believe the question raised implies these circumstances were unexpected.

Here are some things to consider when requirements change on a daily basis:

1) Test resource and time estimations become unreliable simply because requirements are not reliable.  Think about all of the test effort that hinges on the reliability of requirements!  
   a) Learning new requirements or relearning revised requirements
   b) Creating test cases for new or revised requirements
   c) Mapping new or revised requirements to test cases
   d) Prioritizing new or revised test cases
   e) Executing additional test cases

2) If the changing requirements adds functionality, how many more testers will be needed to produce test cases and execute them?

3) Modify the Risks section of the Test Plan to account for the changing requirements. Include a contingency plan and be sure that all stakeholders in the company accepts and signs off on it.

4) A contingency plan might include:
   a) bolstering the test effort with additional testers
   b) extending the duration and number of test cycles
   c) adding regression tests associated with areas that are impacted by changing functionalities

5) The additional cost of doing business with this client must be clearly communicated to upper management.  Management will decide whether this mode of operation (constantly changing requirements) is worthwhile to the company or not.  Perhaps future contracts with this client will include terms for changing requirements.