Executing JavaScript in Selenium Java - Framework Patterns

Framework Mode - Executing JavaScript

Folder Structure

selenium-java-project/
├── src/
│   ├── main/
│   │   └── java/
│   │       └── com/example/utils/
│   │           └── JavaScriptExecutorUtil.java
│   └── test/
│       └── java/
│           └── com/example/tests/
│               └── JavaScriptExecutionTest.java
├── testng.xml
├── pom.xml
└── README.md

This structure separates utility classes (like JavaScript execution helpers) from test classes. The testng.xml file manages test suites.

Test Framework Layers

• Driver Layer: Manages WebDriver setup and teardown (e.g., ChromeDriver, FirefoxDriver).
• Utility Layer: Contains helper classes like JavaScriptExecutorUtil to run JavaScript commands safely.
• Page Object Layer: (Optional) Encapsulates page elements and actions; can use JavaScript execution for complex interactions.
• Test Layer: Contains test classes that call utilities and page objects to perform test scenarios.
• Configuration Layer: Holds environment settings, browser options, and credentials.

Configuration Patterns

• Environment Properties: Use config.properties or system properties to define URLs, browsers, and timeouts.
• Browser Setup: Configure browser type and options in a centralized WebDriver factory class.
• Credentials: Store sensitive data securely outside source code, e.g., environment variables or encrypted files.
• JavaScript Execution Settings: No special config needed, but ensure WebDriver supports JavaScript execution (all modern browsers do).

Test Reporting and CI/CD Integration

• Use TestNG reports for detailed test execution results including pass/fail status.
• Integrate with CI/CD tools like Jenkins or GitHub Actions to run tests automatically on code changes.
• Include screenshots or logs when JavaScript execution fails to help debugging.
• Use Allure or ExtentReports for enhanced, user-friendly test reports.

Best Practices

1. Use JavascriptExecutor interface from Selenium to run JavaScript safely and explicitly.
2. Wrap JavaScript calls in utility methods to reuse and handle exceptions gracefully.
3. Prefer native Selenium commands when possible; use JavaScript only for actions Selenium cannot perform.
4. Keep JavaScript snippets simple and readable; avoid complex scripts inside tests.
5. Validate JavaScript execution results with assertions to ensure expected behavior.

Self Check

Where in this framework structure would you add a new utility method to execute a JavaScript alert popup?

Key Result

Use a utility class with Selenium's JavascriptExecutor interface to run JavaScript commands cleanly within tests.

Practice

1. What is the main purpose of using JavascriptExecutor in Selenium Java?

easy

A. To locate elements on the page using JavaScript selectors

B. To execute JavaScript code directly in the browser during a test

C. To start the Selenium WebDriver session

D. To generate test reports automatically

Solution

1. Step 1: Understand the role of JavascriptExecutor

   JavascriptExecutor allows running JavaScript code inside the browser from Selenium tests.

2. Step 2: Identify the main use case

   It is mainly used to perform actions or retrieve information that Selenium WebDriver cannot do directly.

3. Final Answer:

   To execute JavaScript code directly in the browser during a test -> Option B

4. Quick Check:

   JavascriptExecutor runs JS code in browser [OK]

Hint: Remember: JavascriptExecutor runs JS code inside browser [OK]

Common Mistakes:

• Confusing JavascriptExecutor with element locators
• Thinking it starts WebDriver sessions
• Assuming it generates reports

2. Which of the following is the correct way to cast a WebDriver instance to JavascriptExecutor in Selenium Java?

easy

A. JavascriptExecutor js = driver.executeScript();

B. JavascriptExecutor js = driver.getJavascriptExecutor();

C. JavascriptExecutor js = new JavascriptExecutor(driver);

D. JavascriptExecutor js = (JavascriptExecutor) driver;

Solution

1. Step 1: Recall the casting syntax in Java

   To use JavascriptExecutor, you cast the WebDriver instance like this: (JavascriptExecutor) driver.

2. Step 2: Check each option

   JavascriptExecutor js = (JavascriptExecutor) driver; uses correct casting syntax. The other options are invalid method calls or constructors.

3. Final Answer:

   JavascriptExecutor js = (JavascriptExecutor) driver; -> Option D

4. Quick Check:

   Cast driver to JavascriptExecutor using (JavascriptExecutor) [OK]

Hint: Casting uses (JavascriptExecutor) before driver [OK]

Common Mistakes:

• Using non-existent methods like getJavascriptExecutor()
• Trying to instantiate JavascriptExecutor with new keyword
• Calling executeScript() without casting

3. What will be the output of the following code snippet?

JavascriptExecutor js = (JavascriptExecutor) driver;
String title = (String) js.executeScript("return document.title;");
System.out.println(title);

medium

A. Prints the current page's title

B. Throws a ClassCastException

C. Prints 'undefined'

D. Prints the URL of the page

Solution

1. Step 1: Understand the JavaScript executed

   The script returns document.title, which is the page's title as a string.

2. Step 2: Check the casting and output

   The returned object is cast to String and printed, so it outputs the page title.

3. Final Answer:

   Prints the current page's title -> Option A

4. Quick Check:

   executeScript returns document.title string [OK]

Hint: executeScript returns JS value; cast to String for title [OK]

Common Mistakes:

• Expecting URL instead of title
• Not casting return value to String
• Confusing output with undefined or errors

4. Identify the error in the following code snippet:

JavascriptExecutor js = (JavascriptExecutor) driver;
js.executeScript("arguments[0].click();");

medium

A. Incorrect casting of driver to JavascriptExecutor

B. executeScript method does not exist

C. Missing WebElement argument to click()

D. JavaScript syntax error in the string

Solution

1. Step 1: Analyze the executeScript call

   The script uses arguments[0].click(); which requires a WebElement passed as an argument.

2. Step 2: Check the method call parameters

   No WebElement is passed to executeScript, so it will fail at runtime.

3. Final Answer:

   Missing WebElement argument to click() -> Option C

4. Quick Check:

   arguments[0] needs a WebElement passed [OK]

Hint: Pass WebElement as argument when using arguments[0] [OK]

Common Mistakes:

• Forgetting to pass WebElement argument
• Assuming casting is wrong
• Thinking executeScript method is missing

5. You want to scroll a page to a specific WebElement using JavaScript in Selenium Java. Which code snippet correctly achieves this?

hard

A. js.executeScript("arguments[0].scrollIntoView(true);", element);

B. js.executeScript("window.scrollTo(element);");

C. js.executeScript("scrollToElement(arguments[0]);", element);

D. js.executeScript("document.scrollTo(arguments[0]);");

Solution

1. Step 1: Recall JavaScript method to scroll to element

   The correct JS method is scrollIntoView(true) called on the element.

2. Step 2: Check the Selenium executeScript usage

   Pass the WebElement as an argument and use arguments[0].scrollIntoView(true); to scroll.

3. Final Answer:

   js.executeScript("arguments[0].scrollIntoView(true);", element); -> Option A

4. Quick Check:

   Use scrollIntoView with element argument [OK]

Hint: Use arguments[0].scrollIntoView(true) with element [OK]

Common Mistakes:

• Using window.scrollTo with element (invalid)
• Calling non-existent scrollToElement function
• Not passing element as argument