Skip to main content

Impact Analysis

Impact Analysis analyses the import on software when the changes deploy over the software.  Impact Analysis mentioned to perform Regression Testing while changes deploy over the software and some part of software unintentionally failed.

Suppose after completion of a software, if another module is to be added, then we need to test the new module as well as the impacted area which is affected by adding a new module.

Team Lead will ask from the Developer Team, Client and the Test Team regarding the impacted area whenever a new module is add and some changes deploy over the software.

Impact Analysis is a process to find the impact area of the application by adding a new module or new changes.

Impact analysis is required when :

1. Performing Testing after the added bugs has been fixed
2. New changes deploy over the Application
3. New Module added into the Application

Impact analysis in software testing is the process of understanding the complete effect of a particular change in order to determine how this change will impact the testing process.


Labels:

Comments

Post a Comment

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.
Post a Comment
Read more

Ad-Hoc Testing

Ad-Hoc Testing is the testing type which is performed without any proper procedure and without any Requirement Specification. Ad-Hoc testing is totally informal testing which have intension to break the application as early as possible and found important defect early.  In Ad-hoc testing tester do not have any test cases so only the users who have very high knowledge regarding the application only they can perform Ad-Hoc Testing.
Post a Comment
Read more

Smoke Testing

In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.
Post a Comment
Read more