+
+ | Requirements |
+ Details |
+
+
+ | Machine Specifications: |
+
+
+ | CPU |
+ 16 Core |
+
+
+ | RAM |
+ 64 GB & above |
+
+
+ | Storage |
+ Option 1: 512GB - 2TB single storage
Option 2: 256GB + 1TB & above mounted disk
Note: For both storage options, scheduled image backups are recommended. |
+
+
+ | Database Requirements: |
+
+
+ | CPU |
+ 4 Core |
+
+
+ | RAM |
+ 32 GB |
+
+
+ | RDBMS |
+ MySQL |
+
+
+ | Version |
+ 8.0.x |
+
+
+ | Note: Testsigma provides a MySQL Docker container. If you want a hosted MySQL, ensure it meets the above specifications. |
+
+
+ | Machine Configuration: |
+
+
+ | OS |
+ Install Ubuntu at the root with a 256GB machine. |
+
+
+ | Additional Storage |
+ Mount a 2TB (or above, based on usage) hard disk for storage. |
+
+
+ | Software Installation |
+ All required software will be installed at the root, with storage configurations set to utilize the mounted disk. |
+
+
+ | Mount Point |
+ Mount the external disk at /data. |
+
+
+ | File System |
+ You can choose any file system available based on expertise and requirements. |
+
+
+ | Hard Disk Performance |
+ Improved using RAID configuration (optional). |
+
+
+ | Backup Recommendations: |
+
+
+ | Frequency |
+ Backup every 24 hours. |
+
+
+ | Retention |
+ Maintain backups for 1 week. |
+
+
+ | Cleanup |
+ Periodically clean up old data to maintain disk health and space. Additional hardware may be required for longer data retention, which can be attached to the existing mount point using LVM. |
+
+
+ | Note: Recommendations are subject to adjustment based on customer requirements, and installation costs may vary based on these adjustments. |
+
+
+ | Pre-Checks: |
+
+
+ | Internet Connection |
+ Ensure an active internet connection to the server machine. |
+
+
+ | Firewall Configuration |
+ If a firewall is enabled, whitelist the following domains:
*.docker.com
*.amazon.com
*.amazonaws.com
*.maven.org
For using Testsigma's mail service, whitelist *.sendgrid.com. |
+
+
+ | Unblock Ports |
+ Unblock the following ports if they are blocked: 3307, 7010, 8080, 8082, 8084, 9090, 9095, 9096, 9097, 4201, 4203, 4211, 4230.
Testsigma services use these ports for internal communication. (Details Below) |
+
+
+ | Ports Required by Testsigma Micro-Services: |
+
+
+ | testsigma_mysql |
+ 3307 |
+
+
+ | testsigma_id_server |
+ 8084, 9095 |
+
+
+ | testsigma_id_server_ui |
+ 4203 |
+
+
+ | testsigma_app_server |
+ 8080, 9096 |
+
+
+ | testsigma_groot_ui |
+ 4211 |
+
+
+ | testsigma_addon_server |
+ 8082, 9097 |
+
+
+ | testsigma_addon_server_ui |
+ 4201 |
+
+
+ | testsigma_audit_server |
+ 9090 |
+
+
+ | testsigma_audit_ui |
+ 4230 |
+
+
+ | testsigma_visual_testing_server |
+ 7010 |
+
+
+ | Additional Requirements: |
+
+
+ | Agent Operating System |
+ Depending on user preference, the agent can run on Linux, Windows, or Mac machines. |
+
+
+ | Final Storage Location |
+ The final storage location for screenshots, apps, and other permanent files is the host server where Testsigma containers run. |
+
+
+ | Temporary Files |
+ Temporary files like screenshots may need periodic cleaning depending on usage and disk space availability. |
+
+
+ | Windows Machines |
+ The server operation does not require any Windows machines. |
+
+
+ | Data Backups |
+ Customer IT teams must regularly perform data backups through regular disk or specific data folder backups. |
+
+
+ | Hypervisor-based Installation |
+ Testsigma On-Prem Server is not a hypervisor-based installation. |
+
+
+ | Domain Name Customization |
+ By default, the customer would be provided URLs ending with testsigmaprivate.com (like https://cx.testsigmaprivate.com).
If the customer desires to have these pointed to their domain name (like cx.com), then we need the following:
+ Inform Testsigma before the On-prem build is generated.
+ Get the SSL certificates of the domain in interest and copy them to the server where installation would happen. |
+
+
+ | Testsigma Recorder Installation |
+ For installing Testsigma Recorder on Chrome browsers:
+ We need the ability to enable developer mode and install the Testsigma recorder in unpacked mode. |
+
+
+ | SMTP Settings |
+ Customers need to produce their SMTP settings in case they desire to use their internal SMTP instead of Testsigma SMTP servers. |
+
+
+
+
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/on-premise-setup/pre-installation/testsigma-on-prem-architecture.md b/src/pages/docs/on-premise-setup/pre-installation/testsigma-on-prem-architecture.md
new file mode 100644
index 00000000..143048c5
--- /dev/null
+++ b/src/pages/docs/on-premise-setup/pre-installation/testsigma-on-prem-architecture.md
@@ -0,0 +1,126 @@
+---
+title: "Testsigma's On-Premise Architecture"
+order: 26.11
+page_id: "Testsigma's On-premise Architecture"
+metadesc: "Learn how Testsigma on-premise system architecture provides a secure environment for creating and executing automated tests within your organization's local infrastructure"
+noindex: false
+search_keyword: ""
+warning: false
+contextual_links:
+- type: section
+ name: "Contents"
+- type: link
+ name: "Important Components"
+ url: "#important-components"
+- type: link
+ name: "Interactions"
+ url: "#interactions"
+- type: link
+ name: "Testsigma Central Server Architecture"
+ url: "#testsigma-central-server-architecture"
+---
+
+---
+
+The Testsigma On-Premise System Architecture provides a secure environment for creating and executing automated tests within your organization's local infrastructure. This article discusses Testsigma's On-Premise System Architecture.
+
+This architecture includes three main components:
+1. Client Systems
+2. Central Server
+3. Database
+
+Here’s a high level illustration of Testsigma’s On-prem Architecture:
+
+
+
+---
+
+## **Important Components**
+
+### **1. Client Systems:**
+- **Agents:**
+ - Software programs that are installed on each client system for test creation and execution.
+ - These Agents communicate with test browsers and mobile devices to execute tests, using various ports, including 8383, 8484, 8100, and 5037, and a range from 10000 to 65535.
+ - The Agents send test results to the Central Server.
+
+- **Browsers:**
+ - Browsers on the Client Systems provide users access to the Testsigma application via a web interface for seamless interaction.
+
+### **2. Central Server:**
+ - The Central Server is the main hub of the Testsigma On-Premise System Architecture.
+ - It processes and stores all data received from the Agents.
+ - It provides a web interface to access the Testsigma application.
+ - It communicates with the Database to store and retrieve data and ensures that retrieved data is organized.
+ - It also offers storage capabilities for data and test results.
+
+### **3. Database:**
+ - The Database is the backbone of data storage within the Testsigma On-Premise System Architecture.
+ - It stores all relevant information, including test results, user data, and other necessary details. The Database communicates with the Central Server using TCP on port 3307.
+
+---
+
+## **Interactions**
+
+Here's the detailed explanation of communication between components:
+
+
+
+### **1. Client Access**
+- Clients access the Testsigma application using web browsers and interact with the application's features and functionalities.
+- Communication between the Client and the Central Server happens via HTTPS protocol.
+
+### **2. Agent Communication**
+- The Agent on client machines executes tests on browsers and mobile devices by communicating with the Central Server using HTTPS.
+- The Agent also handles the test execution process and returns the results to the Central Server.
+
+### **3. Central Server to Database**
+- The Central Server communicates with the Database using TCP on port 3307 to store and retrieve necessary data.
+
+---
+
+## **Testsigma Central Server Architecture**
+
+The Testsigma Central Server Architecture is designed within a Docker environment, providing containerization benefits such as isolation, scalability, and easy deployment. The architecture consists of servers responsible for specific tasks and a MySQL database to manage data storage.
+
+
+
+### **Components**
+
+**1. Load Balancer**
+- **Role:** Acts as the entry point to the system, distributing incoming traffic among multiple servers to prevent any single server from becoming a bottleneck.
+
+**2. ID Server**
+- **Role:** Handles user identity, authentication, and authorization services.
+- **Ports:** 8084, 9095, 4203
+
+**3. App Server**
+- **Role:** Manages the main application logic and user requests.
+- **Ports:** 8080, 9096, 4211
+
+**4. Addon Server**
+- **Role:** Supports additional features or plugins that extend the main application functionality.
+- **Ports:** 8082, 9097, 4201
+
+**5. Audit Server**
+- **Role:** Manages logging, monitoring, and auditing of system activities and transactions.
+- **Ports:** 9090, 4230
+
+**6. Visual Testing Server**
+- **Role:** Handles visual testing tasks, such as UI validation and automated visual regression testing.
+- **Port:** 7010
+
+**7. MySQL Database**
+- **Roles:**
+ - Stores all the application data, including user information, transactions, logs, etc.
+ - Communicates with all servers to provide necessary data access.
+- **Port:** 3307
+
+
+### **Interactions**
+**1. Load Balancer:**
+- Routes traffic to the ID, App, Addon, Audit, and Visual Testing servers.
+
+**2. Servers:**
+- Each server interacts with the MySQL database to store and retrieve data as needed.
+
+---
\ No newline at end of file
diff --git a/src/pages/docs/on-premise-setup/prerequisites.md b/src/pages/docs/on-premise-setup/prerequisites.md
deleted file mode 100644
index fb659548..00000000
--- a/src/pages/docs/on-premise-setup/prerequisites.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: "On-Premise Setup Prerequisites"
-order: 26.1
-page_id: "On-premise setup prerequisites"
-metadesc: "This detailed guide will help you understand the prerequisites for Testsigma On-premise setup | Know these details before installing Testsigma On-premise setup"
-noindex: false
-search_keyword: ""
-warning: false
-contextual_links:
-- type: section
- name: "Contents"
-- type: link
- name: "Software, Hardware, and other Requirements"
- url: "#software-hardware-and-other-requirements"
----
-
----
-
-
-This article outlines the essential steps and requirements for a successful on-premise setup. Understanding these prerequisites before installing the software is important to ensure a smooth installation process. So, follow the recommendations and requirements given in this document to avoid any issues during the installation process.
-
-
----
-
-
-
-## **Software, Hardware, and other Requirements**
-
-
-|**Requirements**|**Details**|
-|---|---|
-|**Server Configuration**| Please unblock the ports if blocked. Ports: 3306, 7010, 8080, 8082, 8084, 9090, 9095, 9096, 9097, 4200, 4201, 4203, 4210, 4211, 4220, 4230.|
-
-[[info | **NOTE**:]]
-| - Testsigma will provide a MySQL docker container; if you want to use the hosted MySQL, please acquire one with the above specification.
-| - It is recommended to have a scheduled image backup.
-| - Admin access is necessary for On-Prem installation.
-
-
-
----
\ No newline at end of file
diff --git a/src/pages/docs/salesforce-testing/connected-app.md b/src/pages/docs/salesforce-testing/connected-app.md
index 20ff29e2..810a2d67 100644
--- a/src/pages/docs/salesforce-testing/connected-app.md
+++ b/src/pages/docs/salesforce-testing/connected-app.md
@@ -81,5 +81,11 @@ Creating a connected app is important to link external applications and the Sale
4. For Security Token, go to **My Personal Information > Reset My Security Token** and click on **Reset Security Token**. A new token will be sent to admin mail.
+
+
+
+
+> Refer to this [Salesforce troubleshooting]((https://testsigma.com/docs/troubleshooting/salesforce-testing/most-common-issues/)) guide for the most common issues while creating a connected app.
+
---
\ No newline at end of file
diff --git a/src/pages/docs/test-cases/manage/update-test-case-results-in-a-test-plan.md b/src/pages/docs/test-cases/manage/update-test-case-results-in-a-test-plan.md
index 0fec7ee4..4c28a94b 100644
--- a/src/pages/docs/test-cases/manage/update-test-case-results-in-a-test-plan.md
+++ b/src/pages/docs/test-cases/manage/update-test-case-results-in-a-test-plan.md
@@ -1,9 +1,9 @@
---
-title: "Update Test Case result in a Test Plan"
-metadesc: "This article explains how to update Test Case result in a Test Plan"
+title: "Update Test Case Result in a Test Plan"
+metadesc: "Change the status of test cases in test plan reports to ignore test case result of known issues | This article discusses how to update the status of a test case in a test plan"
noindex: false
order: 4.17
-page_id: "Update Test Case result in a Test Plan"
+page_id: "Update Test Case Result in a Test Plan"
warning: false
contextual_links:
- type: section
@@ -13,32 +13,57 @@ contextual_links:
url: "#steps-to-update-test-case-results"
---
-
-In Testsigma, you can change the status of Test Cases in Test Plan reports. This article discusses how to update the status of a Test Case in a Test Plan.
+---
-Here is a quick GIF demonstrating how to update Test Case results in Test Plans in Testsigma.
+
+
+ 🔴 Flagged Feature:
+
+
This feature is currently flagged. Please get in touch with Testsigma support to enable this feature.
+
-3. On the result type dropdown menu, click on **Test Case Results**.
-
+Here is a quick GIF demonstrating how to update test case results in a test plan.
-4. Hover over the Test case result of which you want to change the status and click on the result you want to update.
-
+
-5. On **Add comments** prompt, add a comment and click on **Update**.
-
-6. Hover over the same Test Case to see the updated status and comment.
-
+---
\ No newline at end of file
diff --git a/src/pages/docs/test-data/data-generators/datefunctions-function-type.md b/src/pages/docs/test-data/data-generators/datefunctions-function-type.md
index 477dc71a..5f8ad79e 100644
--- a/src/pages/docs/test-data/data-generators/datefunctions-function-type.md
+++ b/src/pages/docs/test-data/data-generators/datefunctions-function-type.md
@@ -603,19 +603,19 @@ Here's a comprehensive example using the provided code template. The examples fo
Outputs |
- At most: 30
Unit: DAYS
Format: dd/MM/yyyy |
+ Unit: DAYS
Format: dd/MM/yyyy |
16/06/2024 |
- At most: 60
Unit: DAYS
Format: dd/MM/yyyy |
+ Unit: DAYS
Format: dd/MM/yyyy |
17/05/2024 |
- At most: 90
Unit: DAYS
Format: dd/MM/yyyy |
+ Unit: DAYS
Format: dd/MM/yyyy |
17/04/2024 |
- At most: 45
Unit: DAYS
Format: dd/MM/yyyy |
+ Unit: DAYS
Format: dd/MM/yyyy |
01/06/2024 |
@@ -671,19 +671,19 @@ Here's a comprehensive example using the provided code template. The examples fo
Outputs |
- At most: 30
Unit: DAYS
Format: dd/MM/yyyy |
+ Unit: DAYS
Format: dd/MM/yyyy |
15/08/2024 |
- At most: 60
Unit: DAYS
Format: dd/MM/yyyy |
+ Unit: DAYS
Format: dd/MM/yyyy |
14/09/2024 |
- At most: 90
Unit: DAYS
Format: dd/MM/yyyy |
+ Unit: DAYS
Format: dd/MM/yyyy |
14/10/2024 |
- At most: 45
Unit: DAYS
Format: dd/MM/yyyy |
+ Unit: DAYS
Format: dd/MM/yyyy |
30/08/2024 |
@@ -739,7 +739,7 @@ Here's a comprehensive example using the provided code template. The examples fo
Outputs |
- At most: 30
Unit: DAYS
Reference Date: 10/07/2024
Format: dd/MM/yyyy |
+ Unit: DAYS
Reference Date: 10/07/2024
Format: dd/MM/yyyy |
10/06/2024 |
diff --git a/src/pages/docs/test-data/data-generators/phonenumberfunctions-function-type.md b/src/pages/docs/test-data/data-generators/phonenumberfunctions-function-type.md
index 505d22f8..30d6d757 100644
--- a/src/pages/docs/test-data/data-generators/phonenumberfunctions-function-type.md
+++ b/src/pages/docs/test-data/data-generators/phonenumberfunctions-function-type.md
@@ -100,7 +100,7 @@ Before utilising the different data generator functions, it's essential to under
Select Phone Number
Timeout: 30
- OTP: 1234 |
+ 1234 |
@@ -118,7 +118,7 @@ Before utilising the different data generator functions, it's essential to under
Select Phone Number
Timeout: 120
- OTP: 4982, 789012 |
+ 4982, 789012 |
@@ -127,7 +127,7 @@ Before utilising the different data generator functions, it's essential to under
Select Phone Number
Timeout: 45
- OTP: 45178 |
+ 45178 |
diff --git a/src/templates/page.scss b/src/templates/page.scss
index f056c149..f36e38f2 100644
--- a/src/templates/page.scss
+++ b/src/templates/page.scss
@@ -660,32 +660,156 @@ table{
}
// Cookie banner
-#hs-banner-parent{
- .hs-cookie-notification-position-bottom{
- width: calc(min(28em, 100%)) !important;
- left: calc(min(15em, 100%)) !important;
+#hs-banner-parent {
+ a {
+ color: #09c0a1 !important;
+ &:hover {
+ color: #007d85 !important;
+ text-decoration: underline !important;
+ }
+ }
+ .hs-cookie-notification-position-bottom {
+ width: calc(min(26.5em, 100%)) !important;
+ left: calc(min(18.7em, 100%)) !important;
@media only screen and (max-width: 767px) {
- left: 3%;
- bottom: 2%;
- width: 95%;
- }
- @media only screen and (min-width:768px) and (max-width: 1023px) {
- left: 20%;
- bottom: 10%;
- width: 35%;
- }
- #hs-eu-cookie-confirmation-inner{
- @apply p-8;
- #hs-eu-policy-wording{
- @apply mr-0 mb-4;
+ left: 3% !important;
+ bottom: 2% !important;
+ max-width: 95% !important;
+ }
+ @media only screen and (min-width: 768px) and (max-width: 1023px) {
+ left: 20% !important;
+ bottom: 10% !important;
+ max-width: 35% !important;
+ }
+ #hs-eu-cookie-confirmation-inner {
+ padding: 2rem;
+ #hs-eu-policy-wording {
+ strong {
+ margin: 0 0 1rem 0;
+ font-size: 14px !important;
+ line-height: 24px !important;
+ color: #5f5f5f !important;
+ font-weight: 300 !important;
+ }
+ }
+ #hs-eu-cookie-confirmation-buttons-area {
+ justify-content: center;
+ margin-right: 0;
+ #hs-eu-confirmation-button-group {
+ flex-flow: row;
+ #hs-eu-cookie-settings-button {
+ padding: 10px 25px !important;
+ text-align: center !important;
+ font-size: 14px !important;
+ line-height: 20px !important;
+ border: 0.5px solid #d0d5dd !important;
+ color: #0a1a2a !important;
+ min-width: 12em !important;
+ text-decoration: none !important;
+ }
+ #hs-eu-confirmation-button,
+ #hs-eu-cookie-settings-button {
+ font-weight: 600 !important;
+ border-radius: 5px !important;
+ &:hover {
+ color: white !important;
+ background-color: #007d85 !important;
+ border-color: #007d85 !important;
+ }
+ }
+ }
+ }
+ #hs-eu-decline-button {
+ display: none;
}
- #hs-eu-cookie-confirmation-buttons-area{
- @apply justify-center mr-0;
- #hs-eu-decline-button{
- @apply hidden;
+ }
+ }
+}
+#hs-modal {
+ a {
+ color: #09c0a1 !important;
+ }
+ #hs-modal-introduction {
+ font-size: 16px !important;
+ }
+ #hs-modal-introduction-description {
+ p {
+ font-size: 14px !important;
+ line-height: 24px !important;
+ font-weight: 400 !important;
+ color: #5f5f5f !important;
+ }
+ }
+ #hs-modal-body-container{
+ gap: 0 !important;
+ }
+ #hs-categories-container {
+ padding-top: 20px !important;
+ .hs-category-row {
+ border-top: #d0d5ddbd !important;
+ border-style: solid !important;
+ border-width: 1px 0 0 0 !important;
+ padding: 15px 10px 0 !important;
+ .hs-toggle-switch {
+ width: calc(34px + 2px) !important;
+ height: calc(18px + 2px) !important;
+ .hs-toggle-switch-nob{
+ height: 14px !important;
+ width: 14px !important;
+ }
+ }
+ .hs-toggle-selected-flag{
+ .hs-toggle-switch-nob{
+ left: 56% !important;
}
}
+ .hs-category-label{
+ gap: 5px !important;
+ }
+ }
+ #hs-category-analytics,
+ #hs-category-necessary,
+ #hs-category-advertisement,
+ #hs-category-functionality {
+ span {
+ font-size: 18px !important;
+ line-height: 24px !important;
+ font-weight: 600 !important;
+ }
}
+ .hs-category-description {
+ font-size: 14px !important;
+ line-height: 20px !important;
+ font-weight: 400 !important;
+ color: #5f5f5f !important;
+ }
+ .visible {
+ padding-top: 15px;
+ padding-left: 20px !important;
+ }
+ }
+ .hs-always-active-label {
+ font-size: 14px !important;
+ line-height: 20px !important;
+ font-weight: 600 !important;
+ color: #09c0a1 !important;
+ }
+ #hs-modal-footer-container {
+ #hs-modal-accept-all {
+ order: 2 !important;
+ }
+ #hs-modal-accept-all,
+ #hs-modal-save-settings {
+ font-weight: 600 !important;
+ &:hover {
+ background-color: #007d85 !important;
+ border: #007d85 !important;
+ color: white !important;
+ }
+ }
+ }
+ #hs-modal-footer{
+ padding-top: 12px !important;
}
}