Troubleshoot Test Automation Issues
Open Beta Documentation Amazon offers this technical
documentation as part of a pre-release, open beta. The features described might change as Amazon receives feedback
and iterates on the features. For the most current feature information, see the Release
Notes.
Appium Vega Driver supports UiSelector and XPath locator strategies for identifying elements in apps. However, you might encounter issues while implementing these strategies. Common issues include:
Element not found
Cause:
- Elements exists in DOM but remains invisible.
- Dynamic content loads after page initialization.
- Loading indicators blocks element access.
- Multiple apps are opened causing incorrect captured page source.
Solution:
- Add explicit wait for visibility:
WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10)); wait.until(ExpectedConditions.visibilityOfElementLocated(By.xpath("//button"))); - Implement proper wait strategies:
wait.until(ExpectedConditions.invisibilityOfElementLocated(By.id("loading"))); - Use correct syntax:
// Correct syntax using UiSelector (recommended) driver.find_element('UiSelector', '{"args": {"text": "Login"}}') // Correct syntax using XPath //Text[@text='Login'] -
When dealing with multiple apps:
-
Verify current app context using driver.getContext()
- Switch to correct context if needed:
driver.context("NATIVE_APP") // or appropriate context - Review page source before element location:
String pageSource = driver.getPageSource(); // Verify correct app elements are present - Close unnecessary apps or reset app state before test execution
-
Inconsistent test results
Cause:
- Element becomes invalid after page updates.
- Dynamic IDs and attributes change between test runs.
- Element state changes during execution.
Solution:
- Refresh elements after updates:
element = driver.findElement(By.xpath("//button")); - Use stable attributes:
// Stable "//button[contains(@class, 'login')]" // Unstable "//button[@id='login_123']" - Verify element state:
wait.until(ExpectedConditions.elementToBeClickable(By.xpath("//button")));
Performance issues
Cause:
- Complex XPath expressions.
- Unoptimized element location strategies.
- Repeated element lookups.
Solution:
- Use simple locators:
// Better performance "//button[@text='Login']" // Slower performance "//*/button[contains(@text, 'Log')]/parent::*/child::button" - Use cache elements:
WebElement loginButton = driver.findElement(By.xpath("//button")); loginButton.click();
Framework setup
Cause:
- Incorrect Appium configuration.
- Missing or outdated dependencies.
Solution:
For Java:
- Check if your Appium configuration looks like this:
DesiredCapabilities capabilities = new DesiredCapabilities(); capabilities.setCapability("platformName", "Vega"); - Include required dependencies and update framework version:
<dependency> <groupId>io.appium</groupId> <artifactId>java-client</artifactId> <version>latest.version</version> </dependency>
For Python:
bridge = "vda"
desired_caps = {
"platformName": "Vega",
"appium:automationName": "automation-toolkit/JSON-RPC",
"browserName": "",
"kepler:device": "vda://default"
}
options = AppiumOptions()
for key, value in desired_caps.items():
options.set_capability(key, value)
appium_url = "http://127.0.0.1:4723“
driver = webdriver.Remote(appium_url, options=options)
For JavaScript:
const capabilities = {
platformName: 'Vega',
automationName: 'automation-toolkit/JSON-RPC'
// Add other capabilities as needed
};
const driver = await new webdriver.Builder()
.usingServer('http://localhost:4723/wd/hub')
.withCapabilities(capabilities)
.build();
For Ruby:
caps = {
platformName: 'Vega',
automationName: 'automation-toolkit/JSON-RPC'
# Add other capabilities as needed
}
driver = Appium::Driver.new({
'caps' => caps,
'appium_lib' => {
server_url: 'http://localhost:4723/wd/hub‘
}
}, true)
Related topics
Last updated: Sep 30, 2025
