Share this page

# Change Detection and Resolution Overview

Available for BPT Packaged Apps Kit Users

This section describes how you can detect changes in your packaged app that necessitate modifications to your flows and business process tests, and how you can instruct BPT Packaged Apps Kit to make these modifications automatically.

Change detection and resolution simplify component maintenance, thereby reducing the effort needed to invest in automated testing.

Note:

- If BPT Packaged Apps Kit is not enabled for your project, this feature is not available. Access to BPT Packaged Apps Kit must be provided by your Application Lifecycle Management (ALM) Project Administrator using Project Customization. An administrator can enable BPT Packaged Apps Kit in ALM by by clicking , then selecting Customize > Business Process Test and selecting the Enable BPT Packaged Apps Kit check box. For details, see the Micro Focus Application Lifecycle Management Administrator Guide: Business Process Test Page.

- Unified Functional Testing must be installed with its SAP plug-in to use this feature.

Change Detection Overview

BPT Packaged Apps Kit enables you to run business process tests and flows on a packaged app in Change Detection mode. This enables you to determine how the packaged app has changed since the business process test or flow was built, such as whether controls in the user interface were added, deleted, or changed.

Note: Only business components created using the Learn process can run in Change Detection mode.

Change Resolution Overview

When the test or flow run is finished, you can view the details of these changes in the Change Detection Report. This report provides an indication of the modifications you should make to your test or flow to make sure that it is up-to-date.

For each change detected by BPT Packaged Apps Kit, you can resolve the change in Unified Functional Testing. For details, see the section about detecting and resolving changes using Change Detection mode in the Unified Functional Testing User Guide.

For a list of supported changes and resolutions, see the Unified Functional Testing User Guide.

When changes to a component are detected while running a test or flow in Change Detection mode, Business Process Testing also checks if there are components similar to those containing the changes in other tests or flows in the project. Components are considered similar if they at least represent the same learned screen. If Business Process Testing finds similar components, it sends alerts to the tests and flows that are using the components. The alerts recommend that change detection be run for tests and flows containing those components.

Similar components can be reused. If the component in which a change was detected is a reused component, or the step in which the change was detected is within a reused component, you need to decide where to apply the change resolution. You can choose to apply the resolution to the original component, in which case all tests and flows using that component will be affected. You can alternatively choose to apply the resolution to a copy of the component, and use that copy in your flow instead of the reused component.

Example:

Suppose you are testing a screen for inputting contact information for new customers. The screen contains the fields Name, Address, and Phone Number. You create a test that verifies that information entered in these fields is correctly added to your customer database. Suppose you now add an E-mail Address field to the screen. If you run your test in regular mode, the test may pass and you may not notice that there is an additional field that should be tested. However, if you run the test in Change Detection mode, BPT Packaged Apps Kit notices that the field was added to the screen and suggests adding a step to the component corresponding to the new field. You can then run an updated version of the business process test or flow that includes verification of the additional field.

Similarly, if a field was removed from the screen, BPT Packaged Apps Kit notices that the field was removed, even if no step in the component corresponds to the field. The Change Detection Report suggests updating the component to the changed screen.

https://admhelp.microfocus.com ALM 8942
Tips to improve your search results... ALM Help Center ALM Help Center ALM Help 15.5-15.5.1 All View Local Help Center View Online Help Center back Go back in browser history forward Go forward in browser history Remove search highlights next topic Go to next topic previous topic Go to previous topic Print the current topic Version: