Introduction

QMetry provides an ability to configure an execution command for an automation agent in test suite detail. The command is saved for future use so that you do not have to enter it every time at the time of execution. You can trigger automation scripts directly from the Test Suite Execution tab in the Test Suites module. You can also define parameters, the values of these parameters will get replaced with test suite custom field values during runtime. The command and the arguments are defined as custom fields in test suite details. While triggering the execution, QMetry automatically makes the command to be executed based on the arguments and passes it on to the Automation Agent for triggering.

Use Case:

• Manual testers find it easier as they can execute automated test cases without bothering about writing the script. As the command gets saved, they do not need to remember the command once it is added in the test suite. They can trigger automation scripts that has command and arguments defined in the test suite details.

• An automation tester wants to execute the execution command for Automation Agent directly from the Test Suite > Test Suite Execution tab.

Note: The Automation Agent will just trigger the automation command into the agent machine. You can then import/upload the automation execution results through multiple available methods like calling the Automation API, Maven Plugin, Jenkins/Bamboo agents.

Configure Automation Tool

The project admin can establish the mapping between your QTM Project and the Automation tool that is being used for triggering the execution command.

Once the Automation Agent is configured at the Project level, the Execution Command field becomes visible on the test suite details page and Schedule Automation column starts displaying on the Test Execution tab of the test suite.

Steps:

1. Go to Projects > Project Release / Cycle.

2. Open the Automation Tool tab.

3. Select Automation Agent from the drop-down.

The Automation Agent is configured as an Automation Tool for the project.

Define Execution Command on Test Suite details page or Detail tab

Once the Automation Agent is configured at the Project level, the Execution Command field starts displaying on the test suite details page. You can define the command to be executed through the Automation Agent in this field.

Note: The Execution Command field is visible in the test suite details page only when the Automation Agent is configured as the Automation Tool for the Project.

While execution, the command is picked from the “Execution command” defined at the test suite level. The command is created based on the arguments (custom fields) defined at the test suite details level. At the time of execution, the command is generated with the combination of multiple custom fields defined at the test suite level.

The Execution Command field is editable on the Schedule Automation screen so that you want to edit the command also at run-time.

Schedule Automation column in Test Suite > Test Execution tab

Once the Automation Agent is configured at the Project level, the Schedule Automation column starts displaying on the Test Execution tab of the test suite. The Schedule Automation icon displays details for Automation Agent execution on click.

Go to Test Suite > Test Execution tab.

The Schedule Automation button is provided adjacent to the manual execution button on the Test Execution tab of test suite. The button is enabled for a combination of Release, Cycle, and Platform.

Note: The Schedule Automation column is visible in the test suite only when the Automation Agent is configured as the Automation Tool for the Project.

Clicking on the Schedule Automation button opens the screen to schedule the run through Automation Agent.  

The list of configured Automation Agents is displayed on the screen.

Select the Automation Agent to execute.

→ When the Execution Command is defined in Test Suite > Details.

While execution, the command is picked from the “Execution command” defined at the test suite level. The command is created based on the arguments (custom fields) defined at the test suite details level. At the time of execution, the command is generated with the combination of multiple custom fields defined at the test suite level.

The Execution Command field is editable on the Schedule Automation screen so that you can edit the command at run-time.

→ When the Execution Command is not defined in Test Suite > Details.

If the Execution Command is not defined in the test suite details, the field shows empty on the Schedule Automation screen. You can write and execute the command at run-time similarly as you do from the Automation Agent module.

Schedule the run by clicking on the Schedule button for the Agent. The Agent Status should be “Active” to schedule the run.

You can execute the command now or schedule it later. 

Once the job is scheduled, it is displayed in the Manage Schedule screen with “Scheduled” Status.

Click on the Automation History icon to view the command that is executed or which is scheduled to be executed.

The screen shows the list of scheduled automation runs. Click on the History button to view more details of that particular job.

Command with “In Progress” status.

Command with “Completed” status.

You can download the log file by clicking on the Download icon under the Action column.

Manage Schedule

Users can edit all the commands for the scheduled agent jobs from the Test Execution tab under the Test Suites module.

Steps

1. Go to the Schedule Automation by clicking on the icon.

2. Click on the Manage Schedule icon for the agent.

A. Edit Schedule: Click on the Edit icon to edit the agent schedule.

B. Delete Schedule: Click on the Delete icon to delete the agent schedule.