Window management (maximize, size) in Selenium Java - Framework Patterns

Framework Mode - Window management (maximize, size)

Folder Structure

selenium-java-project/
├── src/
│   ├── main/
│   │   └── java/
│   │       └── com/example/app/pages/
│   │           └── HomePage.java
│   └── test/
│       └── java/
│           └── com/example/tests/
│               ├── BaseTest.java
│               ├── WindowManagementTest.java
│               └── utils/
│                   └── DriverFactory.java
├── testng.xml
└── pom.xml

Test Framework Layers

• Driver Layer: DriverFactory.java manages WebDriver setup and teardown, including browser options.
• Page Objects: Classes like HomePage.java represent web pages and expose methods to interact with UI elements.
• Tests: Test classes such as WindowManagementTest.java contain test methods for window maximize and size operations.
• Utilities: Helper classes for common functions, e.g., waiting, logging, or reading config.
• Configuration: testng.xml and pom.xml define test suites, dependencies, and environment parameters.

Configuration Patterns

• Environment Setup: Use testng.xml to define test groups and parameters like browser type.
• Browser Selection: Pass browser name as a parameter to DriverFactory to create the correct WebDriver instance.
• Window Settings: Tests explicitly call window management methods (maximize, setSize) to control window state.
• Credentials & Secrets: Store sensitive data in environment variables or encrypted files, not in code.

Test Reporting and CI/CD Integration

• Use TestNG built-in reports for test execution results (pass/fail, skipped).
• Integrate with CI tools like Jenkins or GitHub Actions to run tests on code commits.
• Generate HTML reports with plugins like maven-surefire-report-plugin or ExtentReports for detailed logs.
• Configure CI to run tests on multiple browsers and report window management test outcomes.

Framework Design Principles

1. Use Page Object Model: Keep window management calls in test or base test classes, not in page objects.
2. Explicit Window Control: Always maximize or set window size explicitly in tests to avoid flaky UI behavior.
3. Driver Factory Pattern: Centralize WebDriver creation to easily manage browser options and window settings.
4. Parameterize Browser and Window Size: Allow tests to run on different browsers and window sizes via config.
5. Clean Up: Ensure driver.quit() is called after tests to close browser windows properly.

Self Check

Where in this folder structure would you add a new utility method to resize the browser window to a custom dimension?

Key Result

Centralize WebDriver setup and explicitly control browser window size and maximize in tests for reliable UI automation.

Practice

1. What does the maximize() method do in Selenium WebDriver window management?

easy

A. It retrieves the current size of the browser window.

B. It makes the browser window fill the entire screen.

C. It sets the browser window to a custom size.

D. It closes the browser window.

Solution

1. Step 1: Understand the purpose of maximize()

   The maximize() method is used to enlarge the browser window to fill the entire screen.

2. Step 2: Differentiate from other window methods

   Unlike setSize() which sets a custom size, maximize() fills the screen automatically.

3. Final Answer:

   It makes the browser window fill the entire screen. -> Option B

4. Quick Check:

   maximize() = fills screen [OK]

Hint: maximize() fills the screen fully, setSize() sets custom size [OK]

Common Mistakes:

• Confusing maximize() with setSize()
• Thinking maximize() returns window size
• Assuming maximize() closes the window

2. Which of the following is the correct syntax to set the browser window size to 1024x768 in Selenium Java?

easy

A. driver.manage().window().maximize(1024, 768);

B. driver.window().setSize(1024, 768);

C. driver.setSize(1024, 768);

D. driver.manage().window().setSize(new Dimension(1024, 768));

Solution

1. Step 1: Recall correct method to set window size

   In Selenium Java, setSize() requires a Dimension object with width and height.

2. Step 2: Check syntax correctness

   driver.manage().window().setSize(new Dimension(1024, 768)); correctly uses driver.manage().window().setSize(new Dimension(1024, 768));. Other options misuse method names or parameters.

3. Final Answer:

   driver.manage().window().setSize(new Dimension(1024, 768)); -> Option D

4. Quick Check:

   setSize() needs Dimension object [OK]

Hint: Use new Dimension(width, height) inside setSize() [OK]

Common Mistakes:

• Calling maximize() with parameters
• Using setSize() without Dimension object
• Wrong method chaining like driver.window()

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

driver.manage().window().setSize(new Dimension(800, 600));
Dimension size = driver.manage().window().getSize();
System.out.println(size.getWidth() + "," + size.getHeight());

medium

A. 800,600

B. 600,800

C. 0,0

D. Throws a runtime exception

Solution

1. Step 1: Set window size to 800x600

   The code sets the browser window size to width=800 and height=600 using setSize().

2. Step 2: Retrieve and print the window size

   The getSize() method returns the current size, which is then printed as "width,height".

3. Final Answer:

   800,600 -> Option A

4. Quick Check:

   setSize(800,600) then getSize() = 800,600 [OK]

Hint: getSize() returns current size after setSize() [OK]

Common Mistakes:

• Mixing width and height order
• Expecting maximize() effect instead
• Assuming getSize() returns null or error

4. Identify the error in the following Selenium Java code snippet for setting window size:

driver.manage().window().setSize(1024, 768);

medium

A. The method name should be setWindowSize(), not setSize().

B. setSize() cannot be called on driver.manage().window().

C. setSize() requires a Dimension object, not two integers.

D. The code is correct and will run without errors.

Solution

1. Step 1: Check setSize() method parameters

   The setSize() method requires a single Dimension object, not two separate integers.

2. Step 2: Identify the error cause

   Passing two integers directly causes a compile-time error because no matching method exists.

3. Final Answer:

   setSize() requires a Dimension object, not two integers. -> Option C

4. Quick Check:

   setSize() needs Dimension object [OK]

Hint: Always wrap width and height in new Dimension() for setSize() [OK]

Common Mistakes:

• Passing width and height as separate arguments
• Using wrong method name
• Ignoring compile-time errors

5. You want to maximize the browser window and then verify if the window width is greater than 1200 pixels. Which code snippet correctly performs this check in Selenium Java?

hard

A. driver.manage().window().maximize();
Dimension size = driver.manage().window().getSize();
if (size.getWidth() > 1200) {
System.out.println("Width is greater than 1200");
}

B. driver.manage().window().setSize(new Dimension(1200, 800));
Dimension size = driver.manage().window().getSize();
if (size.getWidth() > 1200) {
System.out.println("Width is greater than 1200");
}

C. driver.manage().window().maximize(1200, 800);
Dimension size = driver.manage().window().getSize();
if (size.getWidth() > 1200) {
System.out.println("Width is greater than 1200");
}

D. driver.manage().window().maximize();
Dimension size = driver.manage().window().getSize();
if (size.getHeight() > 1200) {
System.out.println("Width is greater than 1200");
}

Solution

1. Step 1: Maximize the browser window

   Use maximize() without parameters to fill the screen.

2. Step 2: Get window size and check width

   Retrieve size with getSize() and compare width with 1200 pixels.

3. Step 3: Verify correctness of condition and output

   driver.manage().window().maximize(); Dimension size = driver.manage().window().getSize(); if (size.getWidth() > 1200) { System.out.println("Width is greater than 1200"); } correctly checks width > 1200 and prints the message.

4. Final Answer:

   Option A code snippet correctly maximizes and checks width. -> Option A

5. Quick Check:

   maximize() then getSize().getWidth() > 1200 [OK]

Hint: maximize() no params; getSize() then check width [OK]

Common Mistakes:

• Passing parameters to maximize()
• Checking height instead of width
• Using setSize() instead of maximize() for full screen