1. Home
  2. OpKey Help
  3. 26. Advanced OpKey Usage
  4. 26.22 Impact Analysis

26.22 Impact Analysis

Overview:

Impact Analysis is a new feature which is now available in OpKey Web, Accelerator and BPMN. Now, you can easily analyze the impact of any changes done in the lower artifacts (like OR, SR ,Coded FL) which is mapped with upper artifact like Function Library, Model, Test Case & Suite in Published/Approved mode. When you switch the mode of the upper artifacts (Function Library, Model, Test Case or Suite) having added lower artifacts, from Draft to Approved or Published then the state of mapped lower artifacts get also changed respectively. If you change the state of the mapped lower artifacts from Approved/Published to the Draft to make changes, make changes and then save it by switching its state to the Approved/Published state then the corresponding upper artifacts get impacted. This feature allows you to analyze such impacts easily and quickly. You can easily trace the impacted artifacts, analyze impact and do more. You can view the list of impacted artifacts under the UsedBy tab in the dockable panel of the lower artifact in which you have made changes. Here, you can view the hierarchy level of the impacted artifacts. Hierarchy of the impacted artifacts is shown up to two upper levels of the artifact. By clicking on the impacted artifact, you can directly navigate to those artifacts.

Need of Impact Analysis?

Analyzing impact of the changes made to any artifact is important as it may affect the associated artifact. By using this Impact Analysis feature, you can easily analyse the impacted artifacts and effects. This feature was required from a long time as earlier to this analyzing impacts due to changes in the associated artifacts was difficult.

Working with Impact Analysis:

Let us see how to work with the Impact Analysis feature…

Suppose there are some artifacts (OR, FL, TC & Suite). The Object Repository (OR1) objects are associated with the corresponding steps in Function Library (FL1), further Function Library is mapped with the Test Case (TC1) & and Test Case is mapped with two Suites (Suite & Suite1).

  • Here, you can have a look at the Function Library (FL1).

  • Here, you can have a look at the Object Repository (OR1).

  • Here, you can have a look at the Test Case (TC1) which contains Function Library (FL1).

  • Here, you can have a look at the first Suite (Suite1) which contains Test Case (TC1).

  • Here, you can have a look at the second Suite (suite) which contains Test Case (TC1).

  • Let us now witch the state of Suite from Draft to Approved.
  • Click on the state dropdown and select Approved.
  • A popup message appears.
  • Click Yes.

  • You get a popup warning message appears that Suite has been locked. Admin user can change the state mode but cannot edit the data.
  • Click Ok.

  • State of the Suite get changed to Approved.

Note: As Suite is the uppermost artifact and when it’s state is changed from Draft to Approved, then this Suite get locked along with the other associated artifacts (like TC, FL in TC and OR in FL etc.).

  • Let us change the state of the another Suite (containing TC1) from Draft to Published.
  • Click on the State dropdown and select Published.
  • A popup message appears. Click Yes.

  • Another popup message appears that Suite has been locked. Admin user can change the state mode but cannot edit the data.
  • Click Ok.

  • Now go to the lower artifacts which are locked as the upper artifact has already been locked.
  • You can view that the locked FL with changed state as Published.

  • Here, you can view that the state of the Object Repository is also changed from Draft to Published.

  • Let us now change the state of the Function Library (FL1) from Published to Draft so that we can make changes.
  • Click on the state dropdown and select Draft as state.
  • A popup message appears. Click Ok to proceed.

  • Let us now make few changes in this Function Library.
  • Here you can view that a new test step (TypeTextOnEditBox) is added in the bottom, as shown below.
  • Click on Save to save the changes made to this Function Library.

  • Now change the state of this Function Library from Draft to Published.
  • A popup message appears regarding locking this artifact.
  • Click Yes to proceed.

  • Let us now open the associated Object Repository file.
  • A popup message appears that the OR file is locked and admin can change state mode but cannot edit the data.
  • Click Ok.

  • Change the state of the Object Repository from Published to the Draft so that we can make changes.
  • A popup message appears. Click Ok proceed.

  • Now, you can make changes to this Object Repository.
  • Here, some major changes (addition & deletion) have been done in the properties of the object (Company), which is mapped with the newly added test step (TypeTextOnEditBox) in the Function Library, as described above.

  • Here, some other object properties have been changed like Home.
  • Save the Object Repository.

  • Navigate to the UsedBy tab showing under the dockable panel and open it.
  • Here, information showing that the FL1 is impacted due to the changes made to the Object Repository.

  • Click on the View button to view the hierarchy (up to 2 level) of the impacted artifact.
  • Due to changes in the Object Repository, associated FL and TC both are impacted.

  • Let us now open the associated Function Library to analyze the impacts.
  • Here, you can view that Internal Impact tab is glowing with Red color, as shown below.

  • When you click on the Highlight All button, all the impacted test steps get highlighted.
  • Hover mouse on the Impacted Details button view the details.
  • Click on the Highlight button to highlight the impacted steps.
  • Click on Dismiss to dismiss the impacts.

  • Click on View to view the impact level (low, medium & high).

  • Let us now change the state of the Function Library from Published to Draft so that you can make changes.
  • A pop up message appears.
  • Click Yes to proceed.

  • Let us first add a test step (OpenBrowser), uncheck all test steps & save this Function Library.
  • Check all the test steps & save it.
  • Now, let us delete the newly added test step (OpenBrowser) from the Function Library.
  • Click Ok to delete the test step & then save this Function Library.

  • Go to the UsedBy tab in the dockable panel and then click on the View button.
  • Here, you can review the impacted artifacts up to 2 level.

  • Let us open the Test Case to view the impacts.
  • Open the Internal Impact tab from the dockable panel.
  • The Test Case has been impacted directly as well indirectly.

  • The Test Case is impacted indirectly as the associated Function Library was modified.
  • Click on the Highlight All button to highlight all the impacted FLs.
  • Click on the Highlight button corresponding to the direct/Indirect impact to highlight the respective Function Library.
  • You can click on the Dismiss button to dismiss the impacts.

  • The Test Case is impacted directly as the test steps were changed in the associated Function Library.
  • Click on the Impacted Details to view the details of impact.

  • Click on View button of the directly impacted Test Case to review the Impacts level.

  • Open the Suite1.
  • A popup message appears that the Suite is locked and admin can change the state but can not edit the data.
  • Click Ok.

  • Open the Internal Impact tab from the dockable panel.
  • Here, you can view that TC1 has been impacted.

  • The Suite has been impacted indirectly as the associated Test Case (TC1) was impacted as the mapped Function Library was modified/changed.

  • Let us open another Suite (Suite) which is locked.
  • Click Ok.

  • Open the Internal Impact tab from the dockable panel.
  • Here, you can view that TC1 has been impacted.
  • The Suite has been impacted indirectly as the associated Test Case (TC1) was impacted as the mapped Function Library was modified/changed.

 

Was this article helpful to you? Yes No