Skip to content

Conversation

@Nandhini4501
Copy link
Contributor

@Nandhini4501 Nandhini4501 commented Jul 9, 2025

Updated the Installing Testsigma Terminal and the FAQ on the Testsigma Terminal docs as per the ticket https://testsigma.atlassian.net/browse/IDEA-2389

image image

Summary by CodeRabbit

  • Documentation
    • Added a new FAQ addressing issues with launching Testsigma Terminal on Linux using the .appimage file, including troubleshooting steps.
    • Updated installation guide for Testsigma Terminal with new screenshots, simplified instructions, and clarifying notes about login sessions and reporting issues.
    • Removed outdated images and interactive demo for a more streamlined user experience.

Updated the Installing Testsigma Terminal and the FAQ on Testsigma Terminal docs
@Nandhini4501 Nandhini4501 requested a review from bharathk08 July 9, 2025 15:00
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 9, 2025

Walkthrough

The documentation for Testsigma Terminal was updated by streamlining the installation guide, replacing outdated screenshots, removing redundant steps, and adding clarifying notes. Additionally, a new FAQ entry was introduced to address issues with launching the Terminal on Linux using the .appimage file, including troubleshooting guidance.

Changes

File(s) Change Summary
src/pages/docs/live-editor/installing-testsigma-terminal.md Updated installation instructions, replaced screenshots, removed old demo code, added clarifying notes, and simplified the flow.
src/pages/docs/live-editor/faqs-on-testsigma-terminal.md Added new FAQ entry about .appimage launch issues on Linux and provided a troubleshooting workaround.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Docs
    participant Testsigma Terminal

    User->>Docs: Reads installation guide
    Docs->>User: Provides updated steps and screenshots
    User->>Testsigma Terminal: Installs and opens app
    Testsigma Terminal-->>User: Prompts for login
    User->>Testsigma Terminal: Logs in
    Testsigma Terminal-->>User: Registers agent, session valid for 24 hours
    User->>Docs: Reads FAQ if app fails to launch
    Docs->>User: Suggests checking dependencies and retrying
Loading

Suggested reviewers

  • Santhosh-testsigma
  • bharathk08

Poem

In the warren of docs, a fresh path appears,
With screenshots renewed and instructions made clear.
If Linux won’t launch, don’t worry or frown—
Just check dependencies, don’t let it get you down!
For every hop forward, we document anew,
So Testsigma’s journey is easy for you.
🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (5)
src/pages/docs/live-editor/faqs-on-testsigma-terminal.md (1)

155-160: Tighten grammar & spacing in new FAQ entry

Minor editorial fixes improve readability and align with house style (single space after punctuation, consistent pronoun usage, actionable workaround).

-### **14. Why is the Testsigma Terminal not launching on Linux (.appimage file not opening)?**
-
-**Answer:** The issue occurs because Linux users receive the **Testsigma Terminal** in **.appimage** format, which requires all necessary dependencies to be available on the system. If dependencies are missing, the **.appimage** may not run and become unclickable. 
-
-**Workaround:** A quick way to fix is to install the missing dependencies and try again. 
+### **14. Why doesn’t the Testsigma Terminal launch on Linux (.appimage file)?**
+
+**Answer:** This issue occurs because the **Testsigma Terminal** is distributed as an **.appimage**, which relies on system-level dependencies being present. If any are missing, the file may fail to launch and appear unresponsive.  
+
+**Workaround:** Install the missing dependencies (e.g., `libfuse2` on Ubuntu) and then retry launching the file.
src/pages/docs/live-editor/installing-testsigma-terminal.md (4)

69-74: Improve accessibility & clarity for Steps 1–2

  1. Provide descriptive alt-text so screen-reader users understand the images.
  2. “Select the machine configuration” could explicitly mention OS/architecture to avoid ambiguity.
-![Testsigma Terminal](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/terminal/Terminal_1.1.png)
+![Agents page showing the Testsigma Terminal download button](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/terminal/Terminal_1.1.png)

-![Machine configuration](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/terminal/Terminal_2.1.png)
+![Dialog prompting for operating-system and architecture](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/terminal/Terminal_2.1.png)

77-82: Reduce confusion between agent vs. Terminal login wording

“Once you log in to your agent” reads as though the agent, not the web session, is being authenticated. Consider rephrasing and tightening the note.

-[[info | **NOTE**:]]
-| Once you log in to your agent, the session stays valid for 24 hours. Even if you close and reopen the application during this time, the agent will register automatically. After 24 hours, you'll need to log in manually, after which the agent will be registered automatically.
+[[info | **NOTE**:]]
+| After you authenticate with Testsigma, the session remains valid for 24 hours. Closing and reopening the application during this window automatically re-registers the agent. Beyond 24 hours, sign in again to resume automatic registration.

83-90: Streamline step ordering & wording

Step 3 already tells users to open the application; Step 5 then repeats “Open the desktop app.” Merging avoids redundancy and shortens the flow.

-3. Install and open the **Testsigma Terminal** application.
-
-4. Click **Login to Testsigma**. You will be redirected to Testsigma. 
+3. Install the **Testsigma Terminal** application and open it.  
+4. In the desktop window, click **Login to Testsigma** to authenticate in your browser.

 ...

-5. Click **Open the desktop app**. The **Testsigma Terminal** opens. 
+5. After successful login, return to the desktop window; the **Testsigma Terminal** will reopen automatically.

88-90: Add example dependency names to aid troubleshooting

Users often don’t know which logs to attach. Mentioning the default log folder path and an example of required details speeds up support.

-| 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 make sure to include the **App Session ID** and **Debugging ID**. To obtain the Debugging ID, ensure the agent was started through Testsigma.
+| If you encounter issues, click **Report Issue** (left panel). Add a short description, attach the latest file from **Logs** (see FAQ #11 for paths), and include both **App Session ID** and **Debugging ID** (visible when the agent starts through Testsigma).
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ae6b546 and 6d6c21d.

📒 Files selected for processing (2)
  • src/pages/docs/live-editor/faqs-on-testsigma-terminal.md (1 hunks)
  • src/pages/docs/live-editor/installing-testsigma-terminal.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/pages/docs/live-editor/faqs-on-testsigma-terminal.md

[grammar] ~155-~155: Use correct spacing
Context: ... launching on Linux (.appimage file not opening)?** Answer: The issue occurs because Linu...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~157-~157: Use correct spacing
Context: ...he .appimage may not run and become unclickable. Workaround: A quick way to fix is to ...

(QB_NEW_EN_OTHER_ERROR_IDS_5)


[grammar] ~159-~159: Use the right pronoun
Context: ...kable. Workaround: A quick way to fix is to install the missing dependencies ...

(QB_NEW_EN_OTHER_ERROR_IDS_9)


[grammar] ~159-~159: Use correct spacing
Context: ...nstall the missing dependencies and try again. ---

(QB_NEW_EN_OTHER_ERROR_IDS_5)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: CI

@bharathk08 bharathk08 merged commit 3c1a4ac into dev Jul 10, 2025
3 of 4 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Dec 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants