version conflict documentation

Author: Aman1905

docs/hyperexecute-how-to-resolve-version-conflict.md

@@ -0,0 +1,89 @@
+---
+id: hyperexecute-how-to-resolve-version-conflict
+title: How to Resolve Version Conflict Issues
+hide_title: false
+sidebar_label: How to Resolve Version Conflict Issues
+description: How to Perform Group-Based Test Discovery in TestNG
+keywords:
+    - hyperexecute yaml
+    - How to Perform Group-Based Test Discovery in TestNG
+url: https://www.lambdatest.com/support/docs/hyperexecute-how-to-perform-group-based-test-discovery-in-testng/
+site_name: LambdaTest
+slug: hyperexecute-how-to-resolve-version-conflict/
+---
+
+<script type="application/ld+json"
+      dangerouslySetInnerHTML={{ __html: JSON.stringify({
+       "@context": "https://schema.org",
+        "@type": "BreadcrumbList",
+        "itemListElement": [{
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.lambdatest.com"
+        },{
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Support",
+          "item": "https://www.lambdatest.com/support/docs/"
+        },{
+          "@type": "ListItem",
+          "position": 3,
+          "name": "How to Resolve Version Conflict",
+          "item": "https://www.lambdatest.com/support/docs/hyperexecute-how-to-resolve-version-conflict/"
+        }]
+      })
+    }}
+></script>
+Maintaining consistent versions across testing frameworks in your project setup is crucial to avoid runtime errors, compatibility issues, and unexpected behaviors. This guide focuses on specifying framework versions in YAML configuration files and aligning them with the version details in project-specific files like `package.json`, `pom.xml`, `.csproj`, and system environment variables for frameworks like Selenium, Playwright, Puppeteer, Cypress, Maestro, and Appium.
+
+## Why Version Consistency Matters
+When versions defined in YAML configuration files do not match those in project files, it can lead to:
+
+- **Dependency Conflicts :** Incompatibility between framework components, leading to failures.
+- **Runtime Errors :** Unexpected crashes or malfunctions during test execution.
+- **Inconsistent Test Results :** Version mismatches can produce different outcomes or misbehave in automated test cases.
+To prevent these issues, it is recommended to ensure that framework versions match between the YAML pre-steps and project files.
+
+## Framework-Specific Guidelines
+This section provides detailed instructions for version consistency across different frameworks.
+
+### Selenium - Java
+For Java projects using Selenium, TestNG and Cucumber dependencies should match between the YAML pre-steps and the pom.xml file.
+
+- **TestNG :** Ensure the TestNG version in your `pom.xml` matches the version specified in the YAML configuration under [`pre-steps`](https://www.lambdatest.com/support/docs/deep-dive-into-hyperexecute-yaml/#pre):
+```xml
+<dependency>
+    <groupId>org.testng</groupId>
+    <artifactId>testng</artifactId>
+    <version>7.5</version>
+    <scope>test</scope>
+</dependency>
+```
+
+> Always verify compatibility between Java and TestNG versions as specified in TestNG's documentation to avoid compatibility conflicts.
+
+### Selenium/Playwright/Puppeteer/Cypress - JavaScript
+For JavaScript frameworks like Selenium, Playwright, Puppeteer, and Cypress, the framework versions specified in the YAML configuration should align with `package.json`:
+
+```json
+{
+  "dependencies": {
+    "selenium-webdriver": "4.1.0",
+    "cypress": "9.5.0",
+    "playwright": "1.15.0"
+  }
+}
+```
+
+Consistency ensures dependencies are installed with the expected versions, avoiding issues like dependency mismatch and incompatible libraries.
+
+### Selenium/Playwright - C# (.NET)
+For .NET projects, Selenium and Playwright versions should match between the YAML pre-steps and the `.csproj` file, which specifies NuGet packages:
+
+```xml
+<PropertyGroup>
+    <TargetFramework>net6.0</TargetFramework>
+    <OutputType>Library</OutputType>
+</PropertyGroup>
+```

docs/testim-integration.md

@@ -1,7 +1,7 @@
 ---
 id: testim-integration
 title: Testim Integration
-hide_title: true
+hide_title: false
 sidebar_label: Testim
 description: LambdaTest offers integration with Testim to help you perform automated browser testing on 3000+ real browsers and OS.
 keywords:
@@ -39,24 +39,16 @@ slug: testim-integration/
       })
     }}
 ></script>
-
-# Testim Integration
-***
-
 Testim provides an automated testing platform to create stable tests using AI-powered capabilities, along with tools that facilitate scaling quality across your software development process.
 
 Integrating LambdaTest with Testim lets you run Testim automated tests on LambdaTest cloud-based grid across 3000+ real browsers and OS.
 
 ## Prerequisites
----
-
 - Create an account on Testim.
 - Create a LambdaTest account. You can [sign up for free](https://accounts.lambdatest.com/dashboard).
 - Get your LambdaTest Username and Access Key.
 
 ## Setting Up the Grid
----
-
 Shown below are the steps to set up your Grid on Testim.
 
 1. Click on your profile icon > **Grids** button.
@@ -73,8 +65,6 @@ Shown below are the steps to set up your Grid on Testim.
 </video>
 
 ## Recording the Tests
----
-
 Shown below are the steps to record your tests on Testim.
 
 1. Click on **New Test** > **Start Recording**.
@@ -88,8 +78,6 @@ Shown below are the steps to record your tests on Testim.
 </video>
 
 ## Configuring the Capabilities
----
-
 Include the capabilities you wish to use in a `.json` file and ensure this file is located in the same directory as your Testim runner.
 
 ```json
@@ -101,8 +89,6 @@ Include the capabilities you wish to use in a `.json` file and ensure this file
 ```
 
 ## Running the Testim Tests on LambdaTest
----
-
 To execute the tests, check:
 
 * If the Testim CLI is not already installed on your system, use the entire command provided by the Testim CLI or dashboard. 
@@ -125,5 +111,4 @@ To view your test results, navigate to the LambdaTest Web Automation Dashboard.
 <img loading="lazy" src={require('../assets/images/tr-testim.png').default} alt="Web Automation Dashboard" width="1920" height="1080" className="doc_img"/>
 
 
->
-**Note**: To explore additional configuration options, you can execute `testim --help` in PowerShell or bash, which will display further customizations available for writing and executing your test cases.
+> **Note**: To explore additional configuration options, you can execute `testim --help` in PowerShell or bash, which will display further customizations available for writing and executing your test cases.

sidebars.js

@@ -724,6 +724,7 @@ module.exports = {
               "hyperexecute-how-to-run-tests-using-local-selenium-drivers",
               "hyperexecute-how-to-perform-dependent-test-based-discovery",
               "hyperexecute-how-to-perform-group-based-test-discovery-in-testng",
+              "hyperexecute-how-to-resolve-version-conflict"
             ],
           },
           {