{
    "componentChunkName": "component---src-templates-page-jsx",
    "path": "/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot/",
    "result": {"data":{"markdownRemark":{"html":"<br>\n<p><strong>The controls available in the Copilot panel during test case execution.</strong></p>\n<hr>\n<p>This page describes the controls available in the Copilot panel during test case execution.</p>\n<hr>\n<h2 id=\"panel-controls\" style=\"position:relative;\"><a href=\"#panel-controls\" aria-label=\"panel controls permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a><strong>Panel Controls</strong></h2>\n<p>The Copilot panel appears alongside the browser during execution. These controls are always visible in the panel header.</p>\n<table>\n<thead>\n<tr>\n<th align=\"left\">Control</th>\n<th align=\"left\">What it does</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td align=\"left\"><strong>Pause</strong></td>\n<td align=\"left\">Pauses execution at the current step. The Copilot waits until you resume.</td>\n</tr>\n<tr>\n<td align=\"left\"><strong>Back</strong></td>\n<td align=\"left\">Steps back to the previous step.</td>\n</tr>\n<tr>\n<td align=\"left\"><strong>Forward</strong></td>\n<td align=\"left\">Steps forward to the next step.</td>\n</tr>\n<tr>\n<td align=\"left\"><strong>Settings</strong></td>\n<td align=\"left\">Opens session settings.</td>\n</tr>\n<tr>\n<td align=\"left\"><strong>Rec</strong></td>\n<td align=\"left\">Records the current session state as a step.</td>\n</tr>\n<tr>\n<td align=\"left\"><strong>Restart</strong></td>\n<td align=\"left\">Restarts execution from the first step. Shown after steps have been generated.</td>\n</tr>\n<tr>\n<td align=\"left\"><strong>Stop</strong></td>\n<td align=\"left\">Ends the execution session.</td>\n</tr>\n</tbody>\n</table>\n<!-- screenshot: Copilot panel header showing Pause, Back, Forward, Settings, and Rec controls -->\n<hr>\n<h2 id=\"step-tabs\" style=\"position:relative;\"><a href=\"#step-tabs\" aria-label=\"step tabs permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a><strong>Step Tabs</strong></h2>\n<p>The Copilot panel shows two tabs:</p>\n<table>\n<thead>\n<tr>\n<th align=\"left\">Tab</th>\n<th align=\"left\">What it shows</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td align=\"left\"><strong>Manual Steps</strong></td>\n<td align=\"left\">The original manual test case steps. Use this to follow along or to compare with what Copilot is executing.</td>\n</tr>\n<tr>\n<td align=\"left\"><strong>Automated Steps</strong></td>\n<td align=\"left\">The automated steps Copilot is executing. Each step shows its current status.</td>\n</tr>\n</tbody>\n</table>\n<!-- screenshot: Copilot panel showing Manual Steps and Automated Steps tabs -->\n<div class=\"custom-block alert alert-info\"><div class=\"custom-block-heading\"><strong>NOTE</strong>:</div><div class=\"custom-block-body\"><p>Switching to the Automated Steps tab while execution is running does not pause execution.</p></div></div>\n<hr>\n<h2 id=\"step-statuses\" style=\"position:relative;\"><a href=\"#step-statuses\" aria-label=\"step statuses permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a><strong>Step Statuses</strong></h2>\n<p>Each step in the Automated Steps panel shows one of the following statuses during execution.</p>\n<table>\n<thead>\n<tr>\n<th align=\"left\">Status</th>\n<th align=\"left\">What it means</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td align=\"left\">Checkmark (green)</td>\n<td align=\"left\">Step completed successfully.</td>\n</tr>\n<tr>\n<td align=\"left\">Spinner</td>\n<td align=\"left\">Step is currently executing.</td>\n</tr>\n<tr>\n<td align=\"left\">Not started</td>\n<td align=\"left\">Step has not been reached yet.</td>\n</tr>\n<tr>\n<td align=\"left\">Failed</td>\n<td align=\"left\">Step did not complete as expected.</td>\n</tr>\n</tbody>\n</table>\n<hr>\n<h2 id=\"debug-controls\" style=\"position:relative;\"><a href=\"#debug-controls\" aria-label=\"debug controls permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a><strong>Debug Controls</strong></h2>\n<p>The bottom of the Copilot browser shows two debug indicators.</p>\n<table>\n<thead>\n<tr>\n<th align=\"left\">Indicator</th>\n<th align=\"left\">What it does</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td align=\"left\"><strong>Execution Point</strong></td>\n<td align=\"left\">Marks the step where execution is currently paused or running.</td>\n</tr>\n<tr>\n<td align=\"left\"><strong>Debug Point</strong></td>\n<td align=\"left\">A step you configured before launch where execution automatically pauses. Useful for investigating a specific step.</td>\n</tr>\n</tbody>\n</table>\n<!-- screenshot: Bottom of Copilot browser showing Execution Point and Debug Point indicators -->\n<hr>\n<h2 id=\"switching-between-manual-and-automated-steps\" style=\"position:relative;\"><a href=\"#switching-between-manual-and-automated-steps\" aria-label=\"switching between manual and automated steps permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a><strong>Switching Between Manual and Automated Steps</strong></h2>\n<p>The Copilot panel shows two view tabs that you can switch between at any time during execution without interrupting it.</p>\n<ul>\n<li><strong>Manual Steps</strong>: The original manual test case steps. Use this to follow along with what Copilot is executing or to reference the expected behavior at each step.</li>\n<li><strong>Automated Steps</strong>: The automated steps Copilot is currently executing. Each step shows its real-time status.</li>\n</ul>\n<p>Switching between tabs only changes what you see in the panel. It does not pause or stop execution.</p>\n<!-- screenshot: Copilot panel showing Manual Steps and Automated Steps tabs during execution -->\n<hr>\n<h2 id=\"adding-a-new-step\" style=\"position:relative;\"><a href=\"#adding-a-new-step\" aria-label=\"adding a new step permalink\" class=\"anchor before\"><svg aria-hidden=\"true\" focusable=\"false\" height=\"16\" version=\"1.1\" viewBox=\"0 0 16 16\" width=\"16\"><path fill-rule=\"evenodd\" d=\"M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z\"></path></svg></a><strong>Adding a New Step</strong></h2>\n<p>You can add a step during execution from the Automated Steps panel.</p>\n<ol>\n<li>At the bottom of the steps list, click <strong>Add new step</strong>.</li>\n<li>Enter the step details.</li>\n<li>The new step is added to the current session.</li>\n</ol>\n<!-- screenshot: Copilot panel showing Add new step option at the bottom of the steps list -->\n<hr>","frontmatter":{"title":"Execution Controls in Copilot","page_title":"Execution Controls in Copilot","metadesc":"The controls available in the Copilot panel during test case execution — panel controls, step tabs, step statuses, debug controls, and adding a new step.","noindex":false,"contextual_links":[{"type":"section","name":"Contents","url":null},{"type":"link","name":"Panel Controls","url":"#panel-controls"},{"type":"link","name":"Step Tabs","url":"#step-tabs"},{"type":"link","name":"Step Statuses","url":"#step-statuses"},{"type":"link","name":"Debug Controls","url":"#debug-controls"},{"type":"link","name":"Adding a New Step","url":"#adding-a-new-step"}]},"fields":{"slug":"/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot/"}}},"pageContext":{"slug":"/docs/test-management/qi-home/automation/copilot/execution-controls-in-copilot/","prev":{"fields":{"slug":"/docs/test-management/qi-home/automation/copilot/execute-test-case-in-local/"},"frontmatter":{"title":"Execute Test Case in Local","metadesc":"Run a test case with Copilot on your local device or a connected mobile device using Testsigma Terminal, for applications that are not publicly accessible.","canonical":null,"keywords":null,"social_share_summary":null,"social_share_desc":null,"social_share_image":null,"noindex":false}},"next":{"fields":{"slug":"/docs/test-management/qi-home/context-mapping/overview/"},"frontmatter":{"title":"Overview: Developer Context Mapping","metadesc":"An overview of how Developer Context Mapping in Arcus connects GitHub pull requests and CLI coding context to test generation in QI Home.","canonical":null,"keywords":null,"social_share_summary":null,"social_share_desc":null,"social_share_image":null,"noindex":false}}}},
    "staticQueryHashes": ["2855385900","63159454"]}