Skip to content

Commit 63b4067

Browse files
authored
Merge pull request #1056 from Aman1905/stage
ios accessibility
2 parents b6025dd + 30ac924 commit 63b4067

File tree

6 files changed

+114
-69
lines changed

6 files changed

+114
-69
lines changed
99.4 KB
Loading
105 KB
Loading

docs/accessibility-settings-ios.md

Lines changed: 22 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -47,59 +47,29 @@ This document outlines the requirements and testing procedures for accessibility
4747
## Accessibility Settings
4848
The following features are essential to test when ensuring accessibility for mobile apps and web content on iOS devices:
4949

50-
### Text Size Adjustment
51-
- **Requirements :** Implementation of a dropdown menu with size options or a slider control for the text size.
52-
- **Functionality :**
53-
- **1. Real-time Updates :**
54-
- Text size changes must apply immediately
55-
- All text elements should scale proportionally
56-
- No application restart required
57-
- **2. Visual Feedback :**
58-
- Loading indicator must display during backend updates
59-
- Success notification required after completion
60-
- **Testing Checklist :**
61-
- ✅ Control interface is easily accessible
62-
- ✅ Text scaling occurs in real-time
63-
- ✅ Loading animation displays during updates
64-
- ✅ Success notification appears after completion
65-
- ✅ All application text responds to size changes
66-
- ✅ No text overlap or truncation occurs
50+
### Display and Text Size
51+
This section focuses on improving text visibility and contrast to assist users with visual needs.
6752

68-
### Contrast Adjustment
69-
- **Requirements :** Implementation of a high-contrast mode toggle and Binary selection (normal/high contrast)
70-
- **Functionality :**
71-
- **1. Toggle Implementation :**
72-
- Single switch interface
73-
- Clear visual indication of current state
74-
- **2. Real-time Updates :**
75-
- Immediate contrast changes
76-
- System-wide application within the app
77-
- **3. Visual Feedback :**
78-
- Loading indicator during backend processing
79-
- Success notification upon completion
80-
- **Testing Checklist :**
81-
- ✅ Toggle is accessible and clearly labeled
82-
- ✅ Contrast changes apply immediately
83-
- ✅ Loading animation displays during processing
84-
- ✅ Success notification appears after completion
85-
- ✅ All UI elements reflect contrast changes
86-
- ✅ Text remains readable in both states
53+
#### Key Features:
54+
- **Increase Contrast :** Enabling this option enhances the contrast of UI elements against the background, making text and interface components easier to see.
55+
56+
- **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.
57+
58+
- **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.
59+
60+
- **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.
61+
62+
<img loading="lazy" src={require('../assets/images/real-device-app-testing/accessibility-1.png').default} className="doc_img"/>
8763

8864
### Reduce Motion
89-
- **Requirements :** Implementation of motion reduction toggle and integration with iOS accessibility settings.
90-
- **Functionality :**
91-
- **1. Motion Control :**
92-
- Single toggle interface
93-
- Simplified animation transitions
94-
- Reduced motion alternatives
95-
- **2. Visual Feedback :**
96-
- Success notification upon setting update
97-
- **Testing Checklist :**
98-
- ✅ Toggle is accessible and functional
99-
- ✅ Animations are simplified when enabled
100-
- ✅ Transitions use motion-reduced alternatives
101-
- ✅ Success notification appears after toggle
102-
- ✅ Settings persist across app sessions
103-
- ✅ No jarring visual effects present
65+
66+
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.
67+
68+
#### Key Features:
69+
- **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.
70+
- **Parallax Effect Adjustment :** Disabling parallax can create a more stable and comfortable experience, particularly for users prone to motion sickness.
71+
72+
<img loading="lazy" src={require('../assets/images/real-device-app-testing/accessibility-2.png').default} className="doc_img"/>
73+
10474
## Conclusion
105-
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.
75+
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,
Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
---
2+
id: hyperexecute-how-to-resolve-version-conflict
3+
title: How to Resolve Version Conflict Issues
4+
hide_title: false
5+
sidebar_label: How to Resolve Version Conflict Issues
6+
description: How to Perform Group-Based Test Discovery in TestNG
7+
keywords:
8+
- hyperexecute yaml
9+
- How to Perform Group-Based Test Discovery in TestNG
10+
url: https://www.lambdatest.com/support/docs/hyperexecute-how-to-perform-group-based-test-discovery-in-testng/
11+
site_name: LambdaTest
12+
slug: hyperexecute-how-to-resolve-version-conflict/
13+
---
14+
15+
<script type="application/ld+json"
16+
dangerouslySetInnerHTML={{ __html: JSON.stringify({
17+
"@context": "https://schema.org",
18+
"@type": "BreadcrumbList",
19+
"itemListElement": [{
20+
"@type": "ListItem",
21+
"position": 1,
22+
"name": "Home",
23+
"item": "https://www.lambdatest.com"
24+
},{
25+
"@type": "ListItem",
26+
"position": 2,
27+
"name": "Support",
28+
"item": "https://www.lambdatest.com/support/docs/"
29+
},{
30+
"@type": "ListItem",
31+
"position": 3,
32+
"name": "How to Resolve Version Conflict",
33+
"item": "https://www.lambdatest.com/support/docs/hyperexecute-how-to-resolve-version-conflict/"
34+
}]
35+
})
36+
}}
37+
></script>
38+
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.
39+
40+
## Why Version Consistency Matters
41+
When versions defined in YAML configuration files do not match those in project files, it can lead to:
42+
43+
- **Dependency Conflicts :** Incompatibility between framework components, leading to failures.
44+
- **Runtime Errors :** Unexpected crashes or malfunctions during test execution.
45+
- **Inconsistent Test Results :** Version mismatches can produce different outcomes or misbehave in automated test cases.
46+
To prevent these issues, it is recommended to ensure that framework versions match between the YAML pre-steps and project files.
47+
48+
## Framework-Specific Guidelines
49+
This section provides detailed instructions for version consistency across different frameworks.
50+
51+
### Selenium - Java
52+
For Java projects using Selenium, TestNG and Cucumber dependencies should match between the YAML pre-steps and the pom.xml file.
53+
54+
- **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):
55+
```xml
56+
<dependency>
57+
<groupId>org.testng</groupId>
58+
<artifactId>testng</artifactId>
59+
<version>7.5</version>
60+
<scope>test</scope>
61+
</dependency>
62+
```
63+
64+
> Always verify compatibility between Java and TestNG versions as specified in TestNG's documentation to avoid compatibility conflicts.
65+
66+
### Selenium/Playwright/Puppeteer/Cypress - JavaScript
67+
For JavaScript frameworks like Selenium, Playwright, Puppeteer, and Cypress, the framework versions specified in the YAML configuration should align with `package.json`:
68+
69+
```json
70+
{
71+
"dependencies": {
72+
"selenium-webdriver": "4.1.0",
73+
"cypress": "9.5.0",
74+
"playwright": "1.15.0"
75+
}
76+
}
77+
```
78+
79+
Consistency ensures dependencies are installed with the expected versions, avoiding issues like dependency mismatch and incompatible libraries.
80+
81+
### Selenium/Playwright - C# (.NET)
82+
For .NET projects, Selenium and Playwright versions should match between the YAML pre-steps and the `.csproj` file, which specifies NuGet packages:
83+
84+
```xml
85+
<PropertyGroup>
86+
<TargetFramework>net6.0</TargetFramework>
87+
<OutputType>Library</OutputType>
88+
</PropertyGroup>
89+
```

docs/testim-integration.md

Lines changed: 2 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
id: testim-integration
33
title: Testim Integration
4-
hide_title: true
4+
hide_title: false
55
sidebar_label: Testim
66
description: LambdaTest offers integration with Testim to help you perform automated browser testing on 3000+ real browsers and OS.
77
keywords:
@@ -39,24 +39,16 @@ slug: testim-integration/
3939
})
4040
}}
4141
></script>
42-
43-
# Testim Integration
44-
***
45-
4642
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.
4743

4844
Integrating LambdaTest with Testim lets you run Testim automated tests on LambdaTest cloud-based grid across 3000+ real browsers and OS.
4945

5046
## Prerequisites
51-
---
52-
5347
- Create an account on Testim.
5448
- Create a LambdaTest account. You can [sign up for free](https://accounts.lambdatest.com/dashboard).
5549
- Get your LambdaTest Username and Access Key.
5650

5751
## Setting Up the Grid
58-
---
59-
6052
Shown below are the steps to set up your Grid on Testim.
6153

6254
1. Click on your profile icon > **Grids** button.
@@ -73,8 +65,6 @@ Shown below are the steps to set up your Grid on Testim.
7365
</video>
7466

7567
## Recording the Tests
76-
---
77-
7868
Shown below are the steps to record your tests on Testim.
7969

8070
1. Click on **New Test** > **Start Recording**.
@@ -88,8 +78,6 @@ Shown below are the steps to record your tests on Testim.
8878
</video>
8979

9080
## Configuring the Capabilities
91-
---
92-
9381
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.
9482

9583
```json
@@ -101,8 +89,6 @@ Include the capabilities you wish to use in a `.json` file and ensure this file
10189
```
10290

10391
## Running the Testim Tests on LambdaTest
104-
---
105-
10692
To execute the tests, check:
10793

10894
* 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.
125111
<img loading="lazy" src={require('../assets/images/tr-testim.png').default} alt="Web Automation Dashboard" width="1920" height="1080" className="doc_img"/>
126112

127113

128-
>
129-
**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.
114+
> **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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -724,6 +724,7 @@ module.exports = {
724724
"hyperexecute-how-to-run-tests-using-local-selenium-drivers",
725725
"hyperexecute-how-to-perform-dependent-test-based-discovery",
726726
"hyperexecute-how-to-perform-group-based-test-discovery-in-testng",
727+
"hyperexecute-how-to-resolve-version-conflict"
727728
],
728729
},
729730
{

0 commit comments

Comments
 (0)