11.Finding elements in web view: Handling different context using chrome remote debugger

Using Chrome Remote debugger

Only for apps which supports Android version 4.4+ or API level >18. Here important point to note is appium works for API level >17 but chrome remote debugger works for API level >18 i.e we can use this chrome feature for API level>18

1)Type “chrome://inspect/#devices” in chrome browser

2) Open app with enabled webview debugger in device listed with adb

3) Click inspect link and we can inspect elements under webview.

Inspecting Email text input field

Inspecting Password input text field

Inspecting Login submit button field

Writing script to automate WebView

We can follow below 4 steps to automate a webview

• Navigate to a portion of your app where a web view is active
• Call getContext() method which will returns a list of contexts we can access, like ‘NATIVE_APP’ or ‘WEBVIEW_1’
• Call context() method with the id of the context we want to access i.e. WEBVIEW_1 which is the name of webview context of the app .This puts Appium session into a mode where all commands are interpreted as being intended for automating the web view, rather than the native portion of the app. For example, if you run getElementByTagName, it will operate on the DOM of the web view, rather than return UIAElements/MobileElements/Native WebElements.
• To stop automating in the web view context we can simply call the context again with id NATIVE_APP i.e. the name native context of the app.

//  Sample Code for above steps:

/* Vikas garg*/

package GOjek

import org.testng.annotations.Test;

import org.testng.annotations.AfterTest;

import org.testng.annotations.BeforeTest;

import io.appium.java_client.android.AndroidDriver;

import io.appium.java_client.AppiumDriver;

import java.net.MalformedURLException;

import java.net.URL;

import java.util.Set;

import org.openqa.selenium.By;

import org.openqa.selenium.WebElement;

import org.openqa.selenium.remote.DesiredCapabilities;

import org.openqa.selenium.support.ui.ExpectedConditions;

import org.openqa.selenium.support.ui.Select;

import org.openqa.selenium.support.ui.WebDriverWait;

public class WebViewSelendroidApp {

public static AndroidDriver driver;

public static AppiumDriver _driver;

public static DesiredCapabilities cap = new DesiredCapabilities();

@BeforeTest

public void startAppium() throws MalformedURLException, InterruptedException{

System.out.println("setUP() :: driver.AndroidDriver() executed");

cap.setCapability("platformVersion","4.4.4");

cap.setCapability("platformName","Android");

cap.setCapability("deviceName","ZX1B32HNBD");

cap.setCapability("app","C:\\Users\\WebView-test.apk");

driver = new AndroidDriver(new URL("http://127.0.0.1:4725/wd/hub"),cap);

}

@Test

public void AppLogin() throws InterruptedException{

System.out.println("AppLogin() :: driver.start() executed");

By webView = By.className("android.webkit.WebView");

By title = By.id("android:id/title");

WebDriverWait wait = new WebDriverWait(driver,300);

driver.findElement(title).getText();

Set availableContexts1 = driver.getContextHandles();

System.out.println("Total No of Context Found Before reaching WebView = "+ availableContexts1.size());

System.out.println("Context Name is "+ availableContexts1);

//4.1 Navigate to a portion of your app where a web view is active

driver.findElement(By.id("com.mkyong.android:id/buttonUrl")).click();

wait.until(ExpectedConditions.visibilityOfElementLocated(webView));

// 4.2 Call getContext() method which will returns a list of contexts we can access, like 'NATIVE_APP' or 'WEBVIEW_1'

Set availableContexts = driver.getContextHandles();

System.out.println("Total No of Context Found After we reach to WebView = "+ availableContexts.size());

for(String context : availableContexts) {

if(context.contains("WEBVIEW")){

System.out.println("Context Name is " + context);

// 4.3 Call context() method with the id of the context you want to access and change it to WEBVIEW_1

//(This puts Appium session into a mode where all commands are interpreted as being intended for automating the web view)

driver.context(context);

break;

}

}

String input_box_text = driver.findElement(By.id("name_input")).getAttribute("value");

System.out.println("Pre written text inside text box is " + input_box_text);

driver.findElement(By.id("name_input")).clear();

driver.findElement(By.id("name_input")).sendKeys("Amit Jain"); System.out.println("No of dropdown on page "+ driver.findElements(By.xpath("//select")).size());

int size=driver.findElements(By.xpath("//select")).get(0).findElements(By.xpath("//option")).size();

System.out.println("No of Elements in dropdown "+ size);

WebElement car = driver.findElement(By.name("car"));

Select preferedCar=new Select(car);

preferedCar.selectByIndex(2);

System.out.println("Button Value is : " + driver.findElement(By.xpath("/html/body/form/div/input[2]")).getAttribute("value"));

//Key code constant: Back key.

//Constant Value: 4 (0x00000004)

driver.sendKeyEvent(4);

// 4.4 To stop automating in the web view context we can simply call the context again with id NATIVE_APP.

for(String context : availableContexts) {

if(context.contains("NATIVE")){

System.out.println("We are Back to " + context);

driver.context(context);

if (driver.findElement(title).getText().equals("WebViewApp"))

System.out.println("Context Switched");

}

}

}

@AfterTest(alwaysRun= true)

public void tearDown(){

driver.quit();

System.out.println("tearDown() :: driver.quit() executed");

}

} // end of class