Localized Execution of an Action for Testing and Troubleshooting in ACCELQ

Introduction

ACCELQ is the most comprehensive platform for test automation and management. It uses natural English code and self-healing features that have grabbed consumers’ attention. It automates API and web testing effortlessly, making this platform flexible for all.

An Action is a component of a context that uses resources. These resources are made accessible to the users by their owner’s context. You can specify a single action or multiple actions in a particular context. If you specify multiple actions in a particular context, all those actions share resources such as Views, Elements, etc.

Now that we know a little about ACCELQ and Actions in ACCELQ, we will discuss the Localized Execution of an Action for Testing and Troubleshooting in ACCELQ.

Localized Execution of an Action for Testing and Troubleshooting in ACCELQ

Before diving into this topic, we will see where an action exists in the complete hierarchy.

In ACCELQ, a scenario is a unit executed and run through several test cases. These test cases, in turn, provide results that can be used for analysis. A scenario contains multiple steps, and with each step occurs an action. You do not run an Action for testing your application, but you run a scenario.

That is why you must be careful while developing a new action or editing a previous one. It is very important to analyze properly whether the Action Logic is performing up to mark or not after the introduced changes.

You can execute an Action at a very basic level for various reasons. This way, you can validate any Action individually and troubleshoot it to generate fast feedback for your Action logic. The best part is it won’t even affect the complete scenario.

To execute an Action, you have open that Action. Simply click the ‘Test’ button in the toolbar at the top of your screen.

Let us see the various aspects associated with the Localized Execution of an Action for testing and troubleshooting in ACCELQ.

Actions that involve UI Testing

There are some actions in ACCELQ that involves interface testing. These actions include working with a browser or a mobile device. For Localized Execution of an Action for Testing and Troubleshooting in ACCELQ, follow the below steps.

• Select one of the available Init Actions and fill up the required parameter values.
• The run begins, and a browser is opened and packed with the appropriate URL.
• You will be notified with a message asking you to interact manually with the browser. This interaction will direct the browser or application to a page where you want to run this Action. You can use the example screen below for your reference.

• Once you complete all the above steps, click on the ‘Proceed’ button in the dialog.

It is recommended to use a Local Agent while running the Action. A Local Agent is one of those currently running the currently logged-in machine. However, you know that this might not be possible every time.

For Example, when your test application is designed to be loaded on a specific remote box, selecting a remote Local Agent is compulsory. When working with such an application, ensure you get a notification on that remote host. The browser opens in that remote host, and the notification will help you manually interact with the browser.

There may arise a case of infinite wait time at the dialog. To avoid such scenarios, you can specify the maximum timeout for running an Action. Suppose the user does not click the ‘Proceed’ button within the specified time. In that case, the Action continues execution automatically and stops.

Action Parameters

Actions don't need to have any parameters. That means an Action may or may not have parameters. If an Action has input parameters, you will be given the required fields. You will have to fill up the necessary information to proceed further. You can select whether you want to type literal values or choose from the properties for each parameter.

You can recall any parameter values you used while running a test case of an Action. Note that the recall option is available only when you exercise an Action as a part of a scenario and not individually.

Access to Execution Reports

An Action can only store a maximum of 5 recent Execution Reports that you can use for further analysis.

To open any of these reports, click on the dropdown icon on the right side of the ‘Test’ button. You will see a dropdown list containing the report. Select the report you want to analyze and open it.