diff --git a/assets/images/real-device-app-testing/accessibility-1.png b/assets/images/real-device-app-testing/accessibility-1.png new file mode 100644 index 000000000..61b0b64d9 Binary files /dev/null and b/assets/images/real-device-app-testing/accessibility-1.png differ diff --git a/assets/images/real-device-app-testing/accessibility-2.png b/assets/images/real-device-app-testing/accessibility-2.png new file mode 100644 index 000000000..77b9ac229 Binary files /dev/null and b/assets/images/real-device-app-testing/accessibility-2.png differ diff --git a/docs/accessibility-settings-ios.md b/docs/accessibility-settings-ios.md index 4d4e1fb48..0273f72ed 100644 --- a/docs/accessibility-settings-ios.md +++ b/docs/accessibility-settings-ios.md @@ -47,59 +47,29 @@ This document outlines the requirements and testing procedures for accessibility ## Accessibility Settings The following features are essential to test when ensuring accessibility for mobile apps and web content on iOS devices: -### Text Size Adjustment -- **Requirements :** Implementation of a dropdown menu with size options or a slider control for the text size. -- **Functionality :** - - **1. Real-time Updates :** - - Text size changes must apply immediately - - All text elements should scale proportionally - - No application restart required - - **2. Visual Feedback :** - - Loading indicator must display during backend updates - - Success notification required after completion -- **Testing Checklist :** - - ✅ Control interface is easily accessible - - ✅ Text scaling occurs in real-time - - ✅ Loading animation displays during updates - - ✅ Success notification appears after completion - - ✅ All application text responds to size changes - - ✅ No text overlap or truncation occurs +### Display and Text Size +This section focuses on improving text visibility and contrast to assist users with visual needs. -### Contrast Adjustment -- **Requirements :** Implementation of a high-contrast mode toggle and Binary selection (normal/high contrast) -- **Functionality :** - - **1. Toggle Implementation :** - - Single switch interface - - Clear visual indication of current state - - **2. Real-time Updates :** - - Immediate contrast changes - - System-wide application within the app - - **3. Visual Feedback :** - - Loading indicator during backend processing - - Success notification upon completion -- **Testing Checklist :** - - ✅ Toggle is accessible and clearly labeled - - ✅ Contrast changes apply immediately - - ✅ Loading animation displays during processing - - ✅ Success notification appears after completion - - ✅ All UI elements reflect contrast changes - - ✅ Text remains readable in both states +#### Key Features: +- **Increase Contrast :** Enabling this option enhances the contrast of UI elements against the background, making text and interface components easier to see. + +- **Smart Invert :** This option reverses colors on the display, except for media and images. It's designed for users who prefer darker backgrounds without inverting every color on the screen. + +- **Larger Accessibility Settings :** When enabled, this option adjusts interface elements to be larger and more accessible without affecting the core layout of the device’s UI. + +- **Text Size Adjustment :** A slider is provided to adjust the size of the text throughout the system. Users can move the slider to the right for larger text and to the left for smaller text. This feature benefits users who need larger fonts for readability across apps and system interfaces. + + ### Reduce Motion -- **Requirements :** Implementation of motion reduction toggle and integration with iOS accessibility settings. -- **Functionality :** - - **1. Motion Control :** - - Single toggle interface - - Simplified animation transitions - - Reduced motion alternatives - - **2. Visual Feedback :** - - Success notification upon setting update -- **Testing Checklist :** - - ✅ Toggle is accessible and functional - - ✅ Animations are simplified when enabled - - ✅ Transitions use motion-reduced alternatives - - ✅ Success notification appears after toggle - - ✅ Settings persist across app sessions - - ✅ No jarring visual effects present + +The Reduce Motion setting is designed to minimize dynamic animations and motion effects. This can benefit users sensitive to motion or those who prefer a more static display. + +#### Key Features: +- **Reduce Motion of User Interface :** This toggle reduces animations throughout the system, including the parallax effect of icons on the Home Screen and in-app transitions. +- **Parallax Effect Adjustment :** Disabling parallax can create a more stable and comfortable experience, particularly for users prone to motion sickness. + + + ## Conclusion -Testing these accessibility features on iOS devices ensures that mobile apps and web content are inclusive and user-friendly for individuals with various accessibility needs. Implementing real-time changes, visual feedback (loaders/animations), and notifications for updates enhances the user experience and compliance with accessibility standards. \ No newline at end of file +These accessibility settings allow iOS users to customize their device’s interface to match individual needs, improving usability and comfort. Whether adjusting text size or reducing motion, \ No newline at end of file diff --git a/docs/hyperexecute-how-to-resolve-version-conflict.md b/docs/hyperexecute-how-to-resolve-version-conflict.md new file mode 100644 index 000000000..1d3348537 --- /dev/null +++ b/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/ +--- + + +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 + + org.testng + testng + 7.5 + test + +``` + +> 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 + + net6.0 + Library + +``` \ No newline at end of file diff --git a/docs/testim-integration.md b/docs/testim-integration.md index 4dd6b2896..355002767 100644 --- a/docs/testim-integration.md +++ b/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/ }) }} > - -# 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. ## 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. ## 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. Web Automation Dashboard -> -**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. diff --git a/sidebars.js b/sidebars.js index 799a98133..c6ff9eabb 100644 --- a/sidebars.js +++ b/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" ], }, {