Skip to main content
All CollectionsQA Copilot
Training QA Copilot
Training QA Copilot

Train the QA Copilot for automation of test cases in TestCollab

Vishal Vaswani avatar
Written by Vishal Vaswani
Updated this week

Once you have configured the QA Copilot settings for a project, you can use the feature and train it for automation of the test cases.

Training Test Cases

To start training QA Copilot for the test cases in the project, navigate to the test case management page.

Automation fields for test cases

There are three additional fields that are associated with the test cases when you enable QA Copilot. These fields can be shown on the test cases grid, using "Columns" pane.

Automated - It is a flag field that either holds the value "Yes" or "No"

Automation Status - It, as the name suggests, holds the status of automation for the test case.

Last Trained On - Time since the test case was last trained

Status can be:


Automation Ready

In Progress

Automation Failed

Start Training

Click on the test case that needs to be automated. In its view pane, you would notice a new "Automate" button.

At least one step is required to automate a test case.

When you use the "Automate" button, QA Copilot begins the training and runs each and every step one by one. During this, it shows screenshots from the app based on the step being run.

As the training progresses for a test case, there can be more than one attempts to run a step, the reason behind this could be the unavailability of an element mentioned in the step. The reattempts depend on the "Step Training Timeout Limit".

The automation status for the test case during the training remains "In Progress"

Training QA Copilot for a test case in TestCollab

Training Results

After all the steps of a test case are run, or in the event of a step failure, the automation status for the test case gets updated to either "Automation Ready" or "Automation Failed".

You can hover over the "Automate" button to see a drop-down. Options for an automated test case are:

  • View training artifacts - to see the training artifacts for the test case, this mainly includes screenshot(s) taken while training for a step, along with a video of training, for quick reference

  • Train again - to restart the training for the test case from step 1, this will result in the removal of artifacts stored during the previous training, for the test case

  • Remove automation - sets the "Automated" status to "False", this will also result in the removal of artifacts stored during the previous training, for the test case

  • Run timeout - helps change the timeout that will be applied when the test case trained for automation is executed after being added to a test plan and assigned to QA Copilot. By default, the value for run timeout is 30 seconds.

In-line Step Manager

If the project has QA Copilot enabled, then on the test case view pane, you would notice a set of tools available for each step that helps manage the steps. The tools include:

  • Add step

    • will add empty step and expected result entry boxes above the current step

  • Edit step

    • changes can be made in the step. User will have option to apply or cancel the changes done. Clipboard feature can also be used here.

  • Delete step

    • will delete the current step and its expected result

Training QA Copilot for a test case in TestCollab


  • As of the date of writing this article, QA Copilot supports testing of web applications

  • If a test case has been trained earlier and its "Automated" flag is set to "Yes", then any change in steps or expected results will reset the "Automated" flag to "No" and the test case will need to be re-trained

  • Reusable steps can be linked with test cases that need to be automated. However, any change in those reusable steps set will result in the "Automated" flag being set back to "No", if it was earlier "Yes" for all test cases that had the updated reusable steps set linked.

  • Automate will not work for test cases that have been linked from other projects using the "Reusable suites" feature.

  • You need to have a sufficient token balance to train QA Copilot for test cases

Did this answer your question?