Feature Availability: Release 4.2
In ACCELQ, a Scenario is an entity which can be executed to run through different test cases and provide results. Each Scenario is comprised of multiple steps, and a step being an instance of an Action. You do not usually run an Action to test your application.
However, as you develop a new Action or edit an existing Action logic, it is important to get a quick feedback to make sure the Action logic is performing to the requirement.
Localized execution of Action
You can execute an Action locally for unit level validation and for troubleshooting. This provides a quick feedback for your Action logic, rather than running a full Scenario to invoke this Action.
Open relevant Action and simply click on the "Test" button in the top entity toolbar of the Action.
This opens the Run modal where you can configure Run information, including the Application Environment, Agent name etc. Configure this information and click on Run button. This opens up the test report showing the progress of the test.
Providing Parameter values
If the Action requires any Input Parameters, user is prompted to provide sample values for the test run. Remember, parameter values are usually provided in a Test Case when this Action is exercised as part of a Scenario.
Working with Web based Action logic
If the Action logic involves working with a browser, you provide a base URL to start a new browser during execution. When the run begins, a browser is opened and loaded with the provided URL. User is now prompted with a message to navigate the browser to a page where this Action can run.
Manually interact with the browser application and make it ready with the page where the current Action can execute. Once this state is reached, press on "Proceed" button in the prompt dialog.
Note: While running an Action, it is advisable to choose a Local Agent that is running on the currently logged in machine. However, this may not always be possible. For example, your test application may only load on a particular remote box and hence you may have to select a remote Local Agent. When you do this, be sure to check for the prompt message on that remote host, where the browser actually opens.
In order to avoid an indefinite wait at the prompt dialog, you can provide a maximum timeout while you run an Action. During the Action run, if the user does not click "Proceed" button within this timeout, execution resumes automatically.
Access to old Action execution reports
ACCELQ maintains up to 5 recent Action execution reports that you can refer. Click on the dropdown icon to the right of the "Test" button and access these reports.