Skip to content

Modifications by Engineering Team #602

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

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

Modifications by Engineering Team #602

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
153 changes: 93 additions & 60 deletions src/pages/docs/live-editor/faqs-on-testsigma-lite.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,112 +10,145 @@ warning: false
---

---
## **Frequently Asked Questions**

### **1. Can I run the Old Java Agent and the Testsigma Lite on the same machine?**
**Answer:** No, only single agent is allowed.
### **1. Can I run the old Java Agent and Testsigma Lite on the same machine?**

**Answer:** No, only one active agent can run at a time. Testsigma Lite automatically detects and integrates with an existing Java Agent, using it for both Live Editor and test executions.

---

### **2. What are the formats available for Testsigma Lite App installation?**
**Answer:** Testsigma Lite is available in the following formats:
- .dmg (for macOS)
- .msi (for Windows)
### **2. What installation formats are available for Testsigma Lite?**

Additionally, Testsigma Lite can also be distributed in **.zip** and **.tar.gz** formats. However, some enterprise security policies may block these formats.
**Answer:** Testsigma Lite is available in:

- **.dmg** (macOS)

- **.msi** (Windows)

- **.zip** and **.tar.gz** (alternative formats, but may be restricted by enterprise security policies)


---

### **3. What happens to my existing Agent? Will it be upgraded?**
**Answer:** If you have an existing agent and have also installed a new agent through Testsigma Lite, The existing Agent will continue to function. However, some compatibility issues may arise when running multiple agents. Two agents cannot run simultaneously, as first agent will consume the ports.
### **3. Will my existing agent be upgraded when I install Testsigma Lite?**

**Answer:** Yes, Testsigma Lite detects and integrates with the existing agent. If an update is available, the agent is upgraded automatically.

---

### **4. Can the old Agent be converted into the new Testsigma Lite Java Agent?**
**Answer:** If an existing agent is present during Testsigma Lite installation, the system prompts the user to either use the existing agent or install a new one. If the user selects the existing agent, Testsigma Lite will continue using it.
### **4. Can the old Java Agent be converted into the new Testsigma Lite Java Agent?**

**Answer:** Yes, during installation, the old agent is detected, upgraded, and converted into the new Testsigma Lite Java Agent.

---

### **5. If the Old Java Agent was registered but inactive, will the new Testsigma Lite register under the same name?**
**Answer:** No, each Agent will have a unique name and identifier to avoid conflicts.
### **5. If my old Java Agent was registered but inactive, will Testsigma Lite reuse its name?**

**Answer:** If Testsigma Lite does not detect the inactive agent, it installs a new one, requiring re-registration.

---

### **6. What happens if the Old Java Agent becomes active again?**
**Answer:** The system is designed to support multiple agents, but for a single machine only single agent can be active.
### **6. What happens if the old Java Agent becomes active again?**

**Answer:** It cannot become active while Testsigma Lite is running, as only one agent can be active at a time.

---

### **7. Which Agent is used for remote executions or ad-hoc runs?**
**Answer:** Active agent will be used for any type of local execution.
### **7. Which agent is used for remote executions or ad-hoc runs?**

**Answer:** Testsigma Lite integrates with the existing agent, which is used for remote executions, ad-hoc runs, and Live Editor.

---

### **8. How does the Testsigma Lite Java Agent register with Testsigma?**
**Answer:** There is no change in the registration process. For more info, refer to [Setting Up Testsigma Agent Locally](https://testsigma.com/docs/agent/setup-on-windows-mac-linux/).

**Answer:** The registration process remains unchanged. Refer to [Setting Up Testsigma Agent Locally](https://testsigma.com/docs/agent/setup-on-windows-mac-linux/) for details.

---

### **9. Can I start, stop, or restart the Agent from the Testsigma application?**

**Answer:** Not yet. Currently, the agent can only be managed via the Testsigma Lite desktop application.

#### **Managing Testsigma Lite**

- **Stop:** Click **Quit Live Editor**.

- **Start:** Launch **Testsigma Lite** from your applications.

- **Restart:** Stop and restart **Testsigma Lite**.


#### **Managing the Agent**

- **Start:** The agent starts automatically when **Testsigma Lite** launches.

- To start manually:

- Navigate to the **Agent Location**.

- Open **Terminal/Command Prompt**.

- Run: `sh Start.sh`

- **Stop:** The agent runs in the background.

- To stop manually:

- Navigate to the **Agent Location**.

- Open **Terminal/Command Prompt**.

- Run: `sh Stop.sh`

- **Restart:** Relaunch **Testsigma Lite** or click the **Restart** button on the Live Editor homepage.


---

### **9. Can I start, stop, or restart the Agent directly from the Testsigma application?**
**Answer:** This feature is planned for a future release. However, you can manage the Agent only through the Testsigma Lite Desktop application.
### **10. Can I manually start or stop the Agent?**

**A. Managing Testsigma Lite**
- **Stop**: Click **Quit Live Editor** to stop Testsigma Lite.
- **Start**: Search for the **Testsigma Lite** application and launch it.
- **Restart**: Stop and start **Testsigma Lite** again.
**Answer:** Yes, but it is not recommended. The agent is designed to run in the background and stopping it may affect Testsigma Lite’s functionality.

**B. Managing the Agent**
- **Start**: The Agent starts automatically when **Testsigma Lite** is launched.
---

**To start manually:**
- Navigate to the **Agent Location**.
- Open **Terminal/Command Prompt** in the **Agent** folder.
- Run the command: `sh Start.sh`
### **11. How can I collect logs from Testsigma Lite?**

- **Stop**: The Agent runs in the background to support local executions.
**Answer:** Logs are stored locally and can be accessed via a button on the home screen.

**To stop manually:**
- Navigate to the **Agent Location**.
- Open **Terminal/Command Prompt** in the Agent folder.
- Run the command: `sh Stop.sh`
**Manual Log Path:**
`Disk > Users > user_folder > Library > Application Support > Testsigma > Testsigma Lite > Logs > .log file`

- **Restart**: The Agent restarts automatically when **Testsigma Lite** is relaunched.

**To restart manually**: Click the **Restart** button on the **Testsigma Lite** homepage (Live Editor).
[[info | **NOTE**:]] | To access the **Library** folder, unhide hidden folders in your `user_folder`.

---
#### **Shortcut to View Hidden Files:**

### **10. Can I manually start or stop the Agent?**
**Answer:** The Debugger Agent and Java Agent work together as a single entity. Stopping one may affect functionality.
- **Mac:** Press **Command (⌘) + Shift + .** in **Finder**.

- **Windows:** Press **Windows + R**, type `control folders`, go to **View**, and select **Show hidden files, folders, and drives**.


---

### **11. How can I collect logs from the Testsigma Lite?**
**Answer:** Logs are stored locally and can be accessed via a button on the home screen. <br>
**Manual Path for Logs:** *Disk > Users > `user_folder` > Library > Application Support > Testsigma > Testsigma Lite > Logs > .log file*
### **12. If the old agent is running, will I be prompted before installing Testsigma Lite?**

[[info | **NOTE**:]]
| To access **Library** folder in the above path, you need to unhide hidden folders in your `user_folder`.

### **Shortcuts to View Hidden Files:**
- **Mac:** Press **Command (⌘) + Shift + .** in **Finder**. <br>
- **Windows:** Press **Windows + R**, type control folders, go to the **View** tab, and select **Show hidden files, folders, and drives**.
**Answer:** Yes, Testsigma Lite detects existing agents and prompts you to either use the existing agent or install a new one.

---

### **12. If the Old Agent is running, will I be asked for permission before installing the new Testsigma Lite?**
**Answer:** At the start of the installation, Testsigma Lite will detect existing agents on your system and prompts you to either use the existing agent or install a new one.
### **13. Where are the Java Agent files stored on my machine?**

---
**Answer:** **Path:**
`Disk > Users > user_folder > Library > Application Support > Testsigma > Agent > Logs`

### **13. Can I find where the Java Agent files are stored on my machine?**
**Answer:** **Path for Agent Files & Logs:** *Disk > Users > `user_folder` > Library > Application Support > Testsigma > Agent > Logs*
[[info | **NOTE**:]] | To access the **Library** folder, unhide hidden folders in your `user_folder`.

[[info | **NOTE**:]]
| To access **Library** folder in the above path, you need to unhide hidden folders in your `user_folder`.
#### **Shortcut to View Hidden Files:**

### **Shortcuts to View Hidden Files:**
- **Mac:** Press **Command (⌘) + Shift + .** in **Finder**. <br>
- **Windows:** Press **Windows + R**, type control folders, go to the **View** tab, and select **Show hidden files, folders, and drives**.
- **Mac:** Press **Command (⌘) + Shift + .** in **Finder**.

- **Windows:** Press **Windows + R**, type `control folders`, go to **View**, and select **Show hidden files, folders, and drives**.


---
51 changes: 35 additions & 16 deletions src/pages/docs/live-editor/installing-testsigma-lite.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,38 +96,57 @@ Testsigma allows you to fix test case issues instantly using Live Editor. To use

![Remove App](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/Remove_Testsigma_Lite.png)

3. Go to **Disk > Users > `user_folder` > Library > Application Support > Testsigma** and remove **Testsigma** folder.
3. Go to **Disk > Users > `user_folder` > Library > Application Support** and remove **Testsigma** folder.

![Delete Folder](https://s3.amazonaws.com/static-docs.testsigma.com/new_images/projects/applications/Remove_Testsigma_Folder.png)

4. To stop the agent running in the background, follow these steps to find and terminate the process:
$HOME/Library/Application Support/Testsigma/Agent/config/agent.properties

4. To stop the agent running in the background, Run the following command in the terminal:
```bash
cd $HOME/.testsigma/TestsigmaLite/agent/TestsigmaAgent
./stop.sh
```

### **For macOS/Linux**
- Open the **Terminal**.
- Run the following command to get the Process ID (PID): <br>
`lsof -i :8383`
- Copy the PID and use the following command to terminate the process:<br>
`kill -SIGKILL <PID>`
```powershell
cd %user_profile%\.testsigma\TestsigmaLite\agent\TestsigmaAgent
stop.bat
```
&nbsp;

## Instuctions to Force Stop the Agent (If the previous step fails and the agent is still running)

### **For Windows**
- Open PowerShell.
- Run the following command to get the Process ID (PID):<br>
`Get-Process -Id (Get-NetTCPConnection -LocalPort 8383).OwningProcess`
- Copy the PID and use the following command to terminate the process:<br>
`Stop-Process -Id <PID> -Force`
**For macOS/Linux**

* Open the Terminal.

---
* Run the following command to get the Process ID (PID):

```lsof -i :8383```

* Copy the PID and use the following command to terminate the process:

```kill -TERM <PID>```

**For Windows**

* Open PowerShell.
* Run the following command to get the Process ID (PID):

```Get-Process -Id (Get-NetTCPConnection -LocalPort 8383).OwningProcess```
* Copy the PID and use the following command to terminate the process:

```Stop-Process -Id <PID> -Force```

&nbsp;

## **File/Folder Locations of Testsigma Lite**


### **Agent Properties**
- **Windows**: %user_profile%\AppData\Roaming\Testsigma\Agent\config\agent.properties
- **Linux**: $HOME/.testsigma/agent/config/agent.properties
- **Mac**: /$HOME/Library/Application Support/Testsigma/Agent/config/agent.properties
- **Mac**: $HOME/Library/Application Support/Testsigma/Agent/config/agent.properties


### **Remove Testsigma Agent Traces**
Expand Down