diff --git a/assets/images/kaneai-github-app/github-actions-three.png b/assets/images/kaneai-github-app/github-actions-three.png index bdd34fe4a..4394fd506 100644 Binary files a/assets/images/kaneai-github-app/github-actions-three.png and b/assets/images/kaneai-github-app/github-actions-three.png differ diff --git a/docs/playwright-android-guide.md b/docs/playwright-android-guide.md index 9bc4ff9ea..6cbe9f72e 100644 --- a/docs/playwright-android-guide.md +++ b/docs/playwright-android-guide.md @@ -84,7 +84,7 @@ export LT_ACCESS_KEY="YOUR_LAMBDATEST_ACCESS_KEY" | Language | Supported Playwright Versions | |----------|-------------------------------| | **JavaScript (Node.js)** | Up to **v1.59.0** | -| **Java, Python, C#** | Up to **v1.53.2** | +| **Java, Python, C#** | Up to **v1.53.0** | @@ -152,8 +152,8 @@ const { chromium } = require("playwright"); const capabilities = { "LT:Options": { platformName: "android", - deviceName: "Pixel 5", - platformVersion: "11", + deviceName: ".*", + platformVersion: ".*", isRealMobile: true, build: "Playwright Android Build", name: "Playwright Android Test", @@ -216,8 +216,8 @@ const { _android } = require("playwright"); const capabilities = { "LT:Options": { platformName: "android", - deviceName: "Pixel 5", - platformVersion: "11", + deviceName: ".*", + platformVersion: ".*", isRealMobile: true, build: "Playwright Android Build", name: "Playwright Android Test", @@ -301,8 +301,8 @@ def main(): capabilities = { "LT:Options": { "platformName": "android", - "deviceName": "Pixel 5", - "platformVersion": "11", + "deviceName": ".*", + "platformVersion": ".*", "isRealMobile": True, "build": "Playwright Android Build", "name": "Playwright Android Test", @@ -375,8 +375,8 @@ public class PlaywrightAndroidTest { public static void main(String[] args) { Map ltOptions = new LinkedHashMap<>(); ltOptions.put("platformName", "android"); - ltOptions.put("deviceName", "Pixel 5"); - ltOptions.put("platformVersion", "11"); + ltOptions.put("deviceName", ".*"); + ltOptions.put("platformVersion", ".*"); ltOptions.put("isRealMobile", true); ltOptions.put("build", "Playwright Android Build"); ltOptions.put("name", "Playwright Android Test"); @@ -446,8 +446,8 @@ var capabilities = new Dictionary ["LT:Options"] = new Dictionary { ["platformName"] = "android", - ["deviceName"] = "Pixel 5", - ["platformVersion"] = "11", + ["deviceName"] = ".*", + ["platformVersion"] = ".*", ["isRealMobile"] = true, ["build"] = "Playwright Android Build", ["name"] = "Playwright Android Test", diff --git a/docs/smartui-selenium-java-sdk.md b/docs/smartui-selenium-java-sdk.md index 0c1c821c2..2c2250406 100644 --- a/docs/smartui-selenium-java-sdk.md +++ b/docs/smartui-selenium-java-sdk.md @@ -382,6 +382,8 @@ SmartUISnapshot.smartuiSnapshot(driver, "Screenshot Name", options); You can capture screenshots of targeted elements by leveraging various locator mechanisms such as XPath, CSS ID, class, and selectors. This precision-driven approach ensures accurate and specific visual regression testing for your web application's components. +You can also pass a resolved `WebElement` object directly to the `smartuiSnapshot` function. This is especially useful when stable locators (such as IDs or XPaths) are not available, as you can locate the element using any strategy in your test code and pass the reference directly. + @@ -432,6 +434,17 @@ SmartUISnapshot.smartuiSnapshot(driver, "Screenshot Name", options); ``` + + +```java title="This is a sample for your configuration for Java to capture an element by passing a WebElement object." +WebElement element = driver.findElement(By.id("Required ID")); // locate using any strategy +HashMap options = new HashMap<>(); +options.put("element", element); +driver.get("Required URL"); +SmartUISnapshot.smartuiSnapshot(driver, "Screenshot Name", options); +``` + + ## For capturing interactive lazy loading elements diff --git a/docs/timeouts-issues-and-resolutions.md b/docs/timeouts-issues-and-resolutions.md index 0ddd5c30f..7cc45ebdb 100644 --- a/docs/timeouts-issues-and-resolutions.md +++ b/docs/timeouts-issues-and-resolutions.md @@ -96,7 +96,7 @@ Maximum number of test cases that can be queued = n + 150 Queuing timeout could happen because of the below: -**Tests in Queue Taking Too Long to Complete:** Tests are queued for only 10 minutes. If the tests in your queue exceed the 10-minute timeline, they are removed from queue. This aborts the execution of your tests, leading to a timeout error. +**Tests in Queue Taking Too Long to Complete:** Tests are queued for only 15 minutes. If the tests in your queue exceed the 15-minute timeline, they are removed from queue. This aborts the execution of your tests, leading to a timeout error. * * *