junejacz

 Profile Answers by junejacz Questions by junejacz

• Oct 20th, 2005

 

I think it is necessary to test the whole application again.

Inclusion of new module might have done some BAD or GOOD

changes to the whole application

hope it helps

Umashanker

• Oct 28th, 2005

 

Hi,

It depends on the modules effect by the change of the code and adding the code.

You first of all needs to identify the cause of the bug identified, based on which need to identify all the areas can be effected with the fix of that and cover all the areas while testing.

Some times a small change may not require to test entire application and sometimes the small change can effect the entire application.

abdulkadar

• Oct 30th, 2005

 

First of all using Requirement Traceability Matrix find impact of the modification of code in testcases,then update the identified testcases which have impact and excute it ,after testcases are reviewed by Subject Matter expects

balu

• Dec 5th, 2005

 

diff b/w web server and application server. what is production and staging web server

dotronny

• Aug 17th, 2007

 

If one module of code is being modified in an application, I think only modules associated with the module being modified should be retested.

Regression testing could be very cubersome in large applications or projects. in view of this, i would say regression test should be carried out on only those modules associated with the modified module.

mkarthik6482

 Profile Answers by mkarthik6482 

• Aug 25th, 2007

 

It is compulsory to test all the modules because these new changes might have an impact on the other modules of the program.

Krishna.kompella

 Profile Answers by Krishna.kompella 

• Apr 13th, 2010

 

If the same question is been asked in any interview, the answer according to me should be as follows - 

We need to analyse the complexity of the 'Change Request' or 'BUG' which have made the mandatory change to happen in the application Module.

 

Now, we need to analyze what kind of change is is being uptaken. In terms of code and efforts needed by the dev Team. And then, we need to analyze the areas which this bug Impacts, meaning, the areas which the developer touches upon fixing this issue.

So, depending upon this analysis we need to take a call.

If the functionality change is major, then there should a thorough check in all the modules. else, we need to test the changes module intensively and we need to run sanity testing on the remaining application if required. 

Usha_s

 Profile Answers by Usha_s 

• Aug 4th, 2010

 

First check with the requirement traceability matrix, the tc which is getting affected. Give high priority to the affected TC followed by a quick regression