Merge pull request #2984 from surishubham/testmuCom

Testmu com

Author: surishubham

assets/images/hyperexecute/features/abort-job/abort-job.png

@@ -407,6 +407,28 @@ env:
   PLATFORM: windows
 ```
 
+#### Spanish Character Encoding
+
+HyperExecute VMs support Spanish character encoding, ensuring tests with Spanish language content and special characters (e.g., ñ, á, é, í, ó, ú, ü, ¿, ¡) execute correctly. You can configure this using the `env` and `pre` flags in your YAML file.
+
+```yaml
+env:
+  LANG: es_ES.UTF-8
+  LC_ALL: es_ES.UTF-8
+
+pre:
+  - sudo locale-gen es_ES.UTF-8
+  - sudo update-locale LANG=es_ES.UTF-8
+```
+
+:::tip
+If you are using Java-based frameworks, you can also set the encoding via `JAVA_TOOL_OPTIONS`:
+```yaml
+env:
+  JAVA_TOOL_OPTIONS: "-Dfile.encoding=UTF-8"
+```
+:::
+
 ***
 
 ### `runtime`

assets/images/hyperexecute/features/job-list/filters-panel.png

@@ -167,3 +167,48 @@ https://{{private_accounts_base_url}}/org-settings/hyperexecute/git-integration
 The redirect contains the `installation_id` parameter, which is required for configuration.
 
 > **Note:** Only Org Admins can complete this configuration step.
+
+## Multi-Tenant GitHub Support
+
+HyperExecute supports connecting your organization to **multiple GitHub instances** at the same time. This is useful when your team works across both GitHub.com and a private GitHub Enterprise Server (e.g., `ghes.yourcompany.com`).
+
+Each GitHub instance is called a **tenant**, identified by the hostname of the Git provider.
+
+### How It Works
+
+When you create a project, HyperExecute automatically detects the tenant from your repository URL:
+
+| Repository URL | Detected Tenant |
+|---------------|----------------|
+| `https://github.com/my-org/my-repo` | `github.com` |
+| `https://ghes.yourcompany.com/my-org/my-repo` | `ghes.yourcompany.com` |
+
+Each tenant maintains its own:
+- GitHub App configuration (App ID, Installation ID)
+- RSA private key for token generation
+- Short-lived installation access tokens
+
+Credentials are **fully isolated** between tenants — tokens and keys from one GitHub instance are never used for another.
+
+### What You Can Do
+
+- Connect to **multiple GitHub instances** (e.g., GitHub.com + GitHub Enterprise Server)
+- Have **multiple GitHub Apps** on the same tenant for different GitHub organizations
+- Each <BrandName /> org can have **one GitHub App per (tenant + GitHub org name)** combination
+
+### Setup for Non-Default Tenants
+
+For GitHub Enterprise Server or any tenant other than `github.com`:
+
+1. Follow [Approach 2](#approach-2-your-existing-github-app-on-prem) or [Approach 3](#approach-3-private-github-app-on-prem-dedicated-app) to install the GitHub App on your enterprise instance.
+
+2. Create an **org-level secret** for the tenant's private key:
+   `github_app_private_key_<tenant_hostname>`
+   For example, if your GitHub Enterprise Server is `ghes.yourcompany.com`:
+   `github_app_private_key_ghes.yourcompany.com`
+
+3. Complete the registration on the <BrandName /> setup page. The tenant is recorded automatically based on the GitHub App's origin.
+
+:::note
+For the default tenant (`github.com`), the platform's built-in Marketplace GitHub App handles key management automatically — no manual secret creation is needed.
+:::

assets/images/hyperexecute/features/job-list/filters-user-select.png

@@ -2,7 +2,7 @@
 id: hyperexecute-guided-walkthrough
 title: Guided Walkthrough of HyperExecute
 hide_title: false
-sidebar_label: Guided Walkthrough 
+sidebar_label: Guided Walkthrough
 description: Learn how to manage Jobs, configure tunnels, upgrade subscriptions, and access detailed test and job information. Discover the power of custom report, analytic.
 keywords:
   - TestMu AI Hyperexecute
@@ -40,32 +40,47 @@ import BrandName, { BRAND_URL } from '@site/src/component/BrandName';
       })
     }}
 ></script>
-This page gives you a guided walkthrough of all the things on the HyperExecute Dashboard and how you can get the most out of the platform once you have successfully [run your first sample Job](/support/docs/hyperexecute-running-your-first-job/). 
+This page gives you a guided walkthrough of all the things on the HyperExecute Dashboard and how you can get the most out of the platform once you have successfully [run your first sample Job](/support/docs/hyperexecute-running-your-first-job/). The dashboard is built to be **WCAG-compliant**, ensuring an accessible experience for all users.
 
 ## Jobs Page
 
 All the tests on HyperExecute get executed as a Job. All the Jobs can be found on our [Jobs page](https://hyperexecute.lambdatest.com/hyperexecute). Each [Job](/support/docs/hyperexecute-status/#1-job-level-status) has a [`Status`](/support/docs/hyperexecute-status/#3-stage-level-status), a unique `Job Number`, a set of [`Labels`](/support/docs/deep-dive-into-hyperexecute-yaml/#joblabel), info on number of [`Tasks`](/support/docs/hyperexecute-status/#2-task-level-status) executed as part of that Job, and a `Summary` section followed by the details of the `Job Duration` and who initiated the Job.
 
-On this page you have other things such as filters, help center, docs, [secrets management](/support/docs/hyperexecute-how-to-save-and-manage-secrets/) and much more. You can also filter through all of the jobs on the basis of the date, status, type etc.
-
 <img loading="lazy" src={require('../assets/images/hyperexecute/getting_started/guided-walkthrough/1.png').default} alt="Image"  className="doc_img"/>
 
 > Learn more about [Secrets Management](/support/docs/hyperexecute-how-to-save-and-manage-secrets/), getting [User Name and Access Key](/support/docs/hyperexecute-how-to-get-my-username-and-access-key/) from our [Knowledge Base](/support/docs/hyperexecute-knowledge-base/)
 
 ### Top Panel
-    
+
 <img loading="lazy" src={require('../assets/images/hyperexecute/getting_started/guided-walkthrough/3.png').default} alt="Image"  className="doc_img"/>
 
 The top panel contains multiple items:
 
 - **Parallel**: It reflects the number of tasks running parallelly
 - **Queued**: It shows number of the tasks queued and are not yet started.
-- **Configure Tunnel**: Tunnel is used to ensure the security of your data for private websites. 
+- **Configure Tunnel**: Tunnel is used to ensure the security of your data for private websites.
 - **Announcements**: The latest announcements and updates can be found here.
 - **Settings**: Manage all of your account and organisation details in this section.
 - **Upgrade**: You can upgrade your <BrandName /> subscription from here.
-      
-*** 
+
+### Filters
+
+The Jobs page provides a filter bar to narrow down the job list based on the following criteria:
+
+- **Status** — Filter jobs by their current status (Running, Completed, Failed, Aborted, etc.)
+- **Label** — Filter by job labels defined in your YAML configuration.
+- **Users** — Filter jobs by the user who triggered them. This is useful when multiple team members share the same organization and you want to view only your jobs.
+- **Type** — Filter by job type (Selenium, Playwright, Cypress, etc.)
+- **Date** — Filter jobs by date range.
+- **View** — Toggle between different view options (e.g., archived jobs).
+
+<img loading="lazy" src={require('../assets/images/hyperexecute/features/job-list/filters-panel.png').default} alt="Job Filters" className="doc_img"/>
+
+To filter jobs for a specific user, click on the **Users** filter and select the desired user from the dropdown list.
+
+<img loading="lazy" src={require('../assets/images/hyperexecute/features/job-list/filters-user-select.png').default} alt="Filter by User" className="doc_img"/>
+
+***
 
 ## Job Details Page
 
@@ -75,37 +90,38 @@ You can click on a particular Job to navigate to the Job Details Page.
   -   **Job Number** - The Number of your Job.
   -   **Summary** - A brief breakdown of all of your tests on the basis of their status.
   -   **Status** - The status of your Job.
-  -   **Created At** - The date of the creation of the Job.  
+  -   **Created At** - The date of the creation of the Job.
   -   **User** - Your user details who triggered the Job.
   -   **Job Duration**: The time it took to run your entire Job.
   -   **Test Duration**: The time it took to run your tests.
   -   **Type**: The job type (Selenium, Playwright, etc) along with the mode of the job (AutoSplit or Matrix).
+  -   **Git Commit ID** - For jobs triggered via [Workflows](/support/docs/hyperexecute-workflows/) or [sourcePayload](/support/docs/hyperexecute-how-to-configure-sourcePayload/), the git commit hash is displayed in the job metadata, providing traceability to the specific code changes tested.
   -   **[Artifacts](/support/docs/hyperexecute-artifacts/)**: Can be used to configure and generate custom reports and artifacts.
   -   **[Report](/support/docs/hyperexecute-reports/)**: A detailed report for your test execution for the Job.
 - The left side shows all the Tasks (Just-in-time testing environments) that were a part of the Job.
 - Each Task has 3 types of Stages : [Pre stages, Scenario stages, Post stages](/support/docs/hyperexecute-status/#3-stage-level-status).
 
 <!-- > **Note** - You can learn about Job, Tasks and Stages [here](/support/docs/hyperexecute-concepts/). -->
 
-<img loading="lazy" src={require('../assets/images/hyperexecute/getting_started/guided-walkthrough/4.png').default} alt="Image"  className="doc_img"/>
+<img loading="lazy" src={require('../assets/images/hyperexecute/features/job-list/git-commit-id.png').default} alt="Job Details Page" className="doc_img"/>
 
-*** 
+***
 
 ## Test Details
-  
+
 You can access a much more detailed section for your test cases on the Automation dashboard by clicking on the **Test** button.
 
 <img loading="lazy" src={require('../assets/images/hyperexecute/getting_started/guided-walkthrough/5.png').default} alt="Image"  className="doc_img"/>
 
-It provides you with all the necessary data points that you need for your test. 
+It provides you with all the necessary data points that you need for your test.
 
 ### Basic Summary
 You can see the details of your test on the panel on the top of the screen. It contains several details like the browser, the test status, the test name, and more.
 
-- **Test Status**: The status of your test. If the test has passed, the status will be passed.  
-- **Test Name**: The name of your test. You can rename the test, copy the name and see all the tests in the build.  
-- **Test ID**: The test ID of your test. You can copy the test ID by clicking on the **Copy** button. 
-- **Browser**: The browser on which your tests are run. 
+- **Test Status**: The status of your test. If the test has passed, the status will be passed.
+- **Test Name**: The name of your test. You can rename the test, copy the name and see all the tests in the build.
+- **Test ID**: The test ID of your test. You can copy the test ID by clicking on the **Copy** button.
+- **Browser**: The browser on which your tests are run.
 - **OS**: The Operating System on which your tests are run.
 - **Resolution**: The resolution of the screen.
 - **Duration**: The amount of time it took for your test to run.
@@ -127,15 +143,15 @@ You can access the commands involved in the test, and the logs on the right hand
 
 <img loading="lazy" src={require('../assets/images/hyperexecute/getting_started/guided-walkthrough/6.png').default} alt="Image"  className="doc_img"/>
 
->**Note**: You can download the logs by clicking on the Download button on the top right-hand corner of the logs tab. 
+>**Note**: You can download the logs by clicking on the Download button on the top right-hand corner of the logs tab.
 
 ## Test Summary Hyperlink
 
 This introduces clickable links within your **test summary**. When you click on these hyperlinks, it dynamically redirects you to the automation dashboard, providing immediate access to detailed test information corresponding to the specific test status clicked.
 
 Additionally, upon redirection, the automation dashboard opens the relevant tab that aligns with the selected test status, streamlining your experience.
 
-  <img loading="lazy" src={require('../assets/images/hyperexecute/getting_started/guided-walkthrough/16.png').default} alt="Image"  className="doc_img"/> 
+  <img loading="lazy" src={require('../assets/images/hyperexecute/getting_started/guided-walkthrough/16.png').default} alt="Image"  className="doc_img"/>
 
 ### How to Activate Test Summary Hyperlinks
 

assets/images/hyperexecute/features/job-list/git-commit-id.png

@@ -53,7 +53,7 @@ HyperExecute supports secrets at multiple levels:
 | Scope | Access | Use Case |
 |-------|--------|----------|
 | **User-Level** (this doc) | Tied to your individual account, available to all your jobs | Personal credentials, user-specific API keys |
-| **Org-Level** | Shared across all users and projects in the organization, managed by admins | Org-wide API keys, shared access tokens |
+| **[Org-Level](/support/docs/hyperexecute-how-to-save-and-manage-secrets/#org-level-secrets)** *(Enterprise only)* | Shared across all users and projects in the organization, managed by admins | Org-wide API keys, shared access tokens |
 | **[Project-Level](/support/docs/hyperexecute-how-to-manage-project-level-secrets/)** | Scoped to a specific project, shared across all users on the project | Project-specific credentials, team-shared keys |
 
 :::info
@@ -160,6 +160,14 @@ In the above sample YAML file:
 - HyperExecute securely retrieves these secrets from its storage i.e. **HashiCorp Vault** at runtime, ensuring they are not exposed during code sharing or storage.
 :::
 
+## Org-Level Secrets
+
+Org-level secrets are organization-wide secrets that are shared across all projects and users within the organization. They are managed by organization admins and are useful for storing shared credentials like API keys, access tokens, or service account credentials that the entire team needs access to.
+
+:::note
+Org-level secrets are an **enterprise-only** feature. Contact your account team or <span className="doc__lt" onClick={() => window.openLTChatWidget()}>**24×7 chat support**</span> to enable this for your organization.
+:::
+
 <nav aria-label="breadcrumbs">
   <ul className="breadcrumbs">
     <li className="breadcrumbs__item">