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.
Start Training
Click on the test case that needs to be automated. In the test case view pane, you will see an Automate button (the bot icon).
At least one step is required to automate a test case.
Automation workflow followed by QA Copilot
When you click the Automate button, QA Copilot performs the following steps:
The test case is queued for automation, and the automation status is set to Queued.
A banner is displayed to provide real-time information about the ongoing training. This includes:
Training ID
Trigger timestamp
Current status
Artifacts count
Progress
Time taken
Tokens consumed
QA Copilot then begins training by processing each step sequentially, and the automation status changes to In Progress.
During and after training for each step, a screenshot is captured and shown as an artifact.
The same process is followed for expected results.As training progresses, a step may be attempted multiple times. This can happen if an element referenced in the step is unavailable.
If training for all steps completes successfully, the automation status is set to Automation Ready (Success).
If QA Copilot fails to train any step:
Training for the remaining steps is terminated.
A Show Error button becomes available for the failed step.
The automation status is set to Automation Failed.
Users can also stop an ongoing training session. In this case, the automation status is set to Aborted – Failed.
Training Results
You can hover over the Automate button (the bot icon) on top to view a drop-down menu. The available options for an automated test case are:
Train again – Restarts training for the test case from step 1. This action creates a new training session for the test case
Remove automation – Sets the Automated status to False
The Training Log Tab
Details of all QA Copilot training sessions for a test case are listed under the Training Log tab in the test case view.
Information available in this tab includes:
Training ID – unique for each training session
Time since triggered
Result
Test case revision
Ran by
Target URL, tokens consumed, and time taken
Clicking on a row displays the training session details within the test case view, along with the associated artifacts.
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:
Untrained
Automation Ready
In Progress
Automation Failed
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
Facts
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-trainedReusable 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 linkedAutomate will not work for test cases that have been linked from other projects using the "
Reusable suites" featureYou need to have a sufficient token balance to train QA Copilot for test cases