Scribd
Upload
35 views1 page

The Application Is Currently in Production and One Module Require Code Changes, I.e., Change Request. Is Testing The Module-Under-Change Enough To Ensure Quality Delivery, Why or Why Not

Uploaded by

Vinod Sangishetty
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
35 views1 page

The Application Is Currently in Production and One Module Require Code Changes, I.e., Change Request. Is Testing The Module-Under-Change Enough To Ensure Quality Delivery, Why or Why Not

Uploaded by

Vinod Sangishetty
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

#Interviewer: The application is currently in production and one module require

code changes, i.e., Change request. Is testing the module-under-change enough to


ensure quality delivery? Why or Why not?

No. Testing the module-under-change is a must-have whereas the changes might have
an impact on the integration with the other modules. Most of the development teams
follow modular coding wherein same functions are re-used in different modules of
the application. If a change is made to a particular module, it doesn’t guarantee
that the change is isolated to that module.

That’s where ‘Regression Testing’ comes to rescue. After a thorough impact analysis
of the changes, Test team needs to verify all the impacted areas – be it within
same module OR outside it (ensuring that there are no side effects of the code
changes).

Tip: Test team’s understanding and Inputs from the development team are a must to
identify all the impacted areas!

You might also like