Common - Changing Requirements

GeekInterview.com > Interview Questions > Testing > Common

Go To First | Previous Question | Next Question

Common | Question 212 of 248

Changing Requirements

How will you test support based sites where in the requirements of the clients keeps changing on daily basis?

Total Answers and Comments: 6

Last Update: February 22, 2009 Asked by: Sandeep Koul

Sponsored Links

Best Rated Answer

—

Submitted by: rajeshwarash

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.

Above answer was rated as good by the following members:
sreevatsava

March 17, 2008 15:27:45

saransh.kanaujia

Member Since: February 2008 Contribution: 20

RE: Changing Requirements

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.

Is this answer useful? Yes | No

April 15, 2008 12:41:28

G.D.S.Prasad

Member Since: November 2006 Contribution: 191

RE: Changing Requirements

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

Is this answer useful? Yes | No

0 1

Overall Rating: -1

May 17, 2008 16:05:43

rajeshwarash

Member Since: April 2008 Contribution: 8

RE: Changing Requirements

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.

Is this answer useful? Yes | No

1 0

Overall Rating: +1

August 25, 2008 03:40:20

saurabh_saxena1

Member Since: August 2008 Contribution: 4

RE: Changing Requirements

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

Is this answer useful? Yes | No

February 12, 2009 01:26:31

srinivasulub1981

Member Since: December 2005 Contribution: 381

RE: Changing Requirements

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

Is this answer useful? Yes | No

February 22, 2009 15:33:20

vk1978

Member Since: February 2009 Contribution: 174

RE: Changing Requirements

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.

Is this answer useful? Yes | No

Go To Top

User Name		Remember Me?
Password

Question Bank