Skip to content

Updated Components of Testsigma Terminal doc #865

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bharathk08 merged 1 commit into from
Dec 9, 2025
Merged

Updated Components of Testsigma Terminal doc #865

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
63 changes: 54 additions & 9 deletions src/pages/docs/live-editor/components-of-testsigma-terminal.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,52 @@ contextual_links:

---

Testsigma Terminal consolidates everything you need to run tests, access logs, and utilize advanced capabilities in one convenient location. It simplifies execution workflows and ensures you can quickly access the tools and options required during testing. This article discusses the components of Testsigma Terminal.
Testsigma Terminal consists of five core components that enable seamless test automation execution, comprehensive logging, and efficient troubleshooting capabilities.

The Terminal provides a centralized interface for running automated tests, monitoring execution activity, and managing your testing environment. Understanding each component ensures optimal utilization of the platform's capabilities.

**Core Components**
Copy link
Contributor

@coderabbitai coderabbitai bot Dec 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion | 🟠 Major

Convert emphasis to heading to fix markdown lint violation (MD036).

Line 27 uses emphasis (**Core Components**) when it should be a heading since it introduces a section of content. This violates the no-emphasis-as-heading rule and may impact accessibility and document structure.

- **Core Components**
+ ## Core Components
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
**Core Components**
## Core Components
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

27-27: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

🤖 Prompt for AI Agents 
In src/pages/docs/live-editor/components-of-testsigma-terminal.md around line
27, the text currently uses bold emphasis "**Core Components**" instead of a
markdown heading; replace the emphasis with an appropriate heading syntax (e.g.,
"## Core Components" or "### Core Components" to match surrounding heading
levels) so the line is an actual heading and the MD036 lint rule is satisfied.


1. **Copilot :**
The Copilot serves as the primary execution engine for automated tests across Web, Desktop, and Salesforce applications.

**Key Features:**
- Automatically downloads and configures all required dependencies during initial setup.
- Provides real-time execution status through visual indicators (green status indicates active test execution).
- Supports multiple application types within a unified interface.

2. **Agentic :**
The Agentic component powers Atto (Agentic Copilot), an advanced automation capability available exclusively to enterprise users.

**Key Features:**
- Manages dedicated dependency downloads for Atto Copilot functionality.
- Operates independently from the standard Copilot component.
- Provides enhanced automation capabilities for enterprise-level testing scenarios.

3. **Logs :**
The Logs component provides comprehensive debugging and monitoring capabilities through three distinct log categories:
- **Terminal Logs** – System-level operations and terminal activity.
- **Agent Logs** – Agent-specific execution data and communication records.
- **Execution Logs** – Detailed test run information and step-by-step execution data.

This structured approach facilitates efficient troubleshooting and performance analysis.

4. **Info :**
The Info component displays critical system and configuration information:
- Device specifications and hardware details.
- Current version and port configuration.
- Terminal directory file path.
- Quick access to help documentation and support resources.

5. **Report Issue :**
The Report Issue feature streamlines the support process by enabling direct issue submission from the Terminal.

**Key Features:**
- One-click issue reporting.
- Automatic attachment of relevant log files.
- Accelerated resolution through comprehensive diagnostic data.

This article discusses how to navigate and engage with the five essential components that drive the Testsigma Terminal environment.

---

Expand All @@ -44,20 +89,17 @@ Testsigma Terminal consolidates everything you need to run tests, access logs, a
- **Agentic** – displays upgrade availability for Web, Salesforce, and Desktop applications.
Click **Upgrade to Enterprise** to enable enterprise-level Agentic features for the selected application. ![Agentic](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/copilot/copilot_2.png)

2. To view logs, click **Logs** from the left panel.
2. To view logs, click **Logs** from the left panel. The **Logs** page provides a complete overview of debugging information, organized across three tabs for easy access and analysis.
![Logs](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/copilot/copilot_3.png)

The Logs page includes three tabs you can switch between:

- **Terminal Logs** – Displays logs generated by the Testsigma Terminal application.
- **Terminal Logs** – These logs show the status and setup of the Testsigma Terminal app.You will find information about agent and packages installation, system configuration, and the communication status between the Terminal and the Copilot agent.
![Terminal Logs](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/copilot/copilot_4.png)
- **Agent Logs** – Shows logs related to the Agent running on the machine.
- **Agent Logs** – These logs show everything that happens inside the execution agent (Copilot) while it is running a test. This includes the communication records and all the steps taken during test execution.
![Agent Logs](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/copilot/copilot_5.png)
- **Execution Logs** – Contains logs from the execution sessions.
- **Execution Logs** – These logs show the real-time activity for the test you are currently running. You will find specific information related to the execution active in the Live Editor.
![Execution Logs](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/copilot/copilot_6.png)

3. Click **Info** to review the Terminal info page, where you can view your device details,
version and port information, the Terminal directory location, and access help and support resources.
3. Click **Info** to view the information about the Terminal.
![Info](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/copilot/copilot_12.png)

4. If you encounter issues with **Testsigma Terminal**, click **Report Issue** from the left panel.
Expand All @@ -70,4 +112,7 @@ Testsigma Terminal consolidates everything you need to run tests, access logs, a
- Click **Send Report**.
![Send Report](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/copilot/copilot_10.png)

[[info | **NOTE**:]]
| When you report an issue, the relevant logs are automatically attached for easier troubleshooting.

---
4 changes: 2 additions & 2 deletions src/pages/docs/live-editor/installing-testsigma-terminal-on-windows.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,9 +33,9 @@ Copilot is the primary tool for test authoring and validation through local exec
[[info | **NOTE**:]]
| Once you log in, the session stays valid for 24 hours. After that, you'll need to log in and authorize yourself again to continue using the Copilot.

1. Click **Open the desktop app**. The **Testsigma Terminal** opens.
5. Click **Open the desktop app**. The **Testsigma Terminal** opens.

2. Wait until Testsigma Terminal downloads the necessary files and completes the installation.
6. Wait until Testsigma Terminal downloads the necessary files and completes the installation.

[[info | **NOTE**:]]
| If you encounter any issues with the Testsigma Terminal, click Report Issue from the left panel. Provide a description of the problem, upload the agent log, and ensure that you include the App Session ID and Debugging ID. To obtain the Debugging ID, ensure the agent was started through Testsigma.
Expand Down