Why data separation improves test coverage in Selenium Java - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to read test data from an external source.

Selenium Java

String username = [1].getProperty("username");

Drag options to blanks, or click blank then click option'

Aelement

Bdriver

Cconfig

Dpage

Attempts:

3 left

💡 Hint

Common Mistakes

Using driver or element objects to get test data causes errors because they handle browser actions, not data.

Hardcoding values inside test code reduces flexibility and coverage.

The config object holds external test data properties, so using config.getProperty("username") reads the username from data separated from the test code.

2fill in blank

medium

Complete the code to loop through test data rows for multiple test cases.

Selenium Java

for (int i = 0; i < [1].size(); i++) {

Drag options to blanks, or click blank then click option'

AtestData

Bconfig

Celements

Ddriver

Attempts:

3 left

💡 Hint

Common Mistakes

Using driver or elements objects here causes errors because they don't hold test data.

Using config.size() is invalid because config is a properties object, not a list.

The testData list contains multiple data rows. Looping through it allows running tests with different inputs, improving coverage.

3fill in blank

hard

Fix the error in the assertion to compare expected and actual values from separated data.

Selenium Java

assertEquals([1], actualTitle);

Drag options to blanks, or click blank then click option'

AexpectedTitle

Bdriver.getTitle()

CactualTitle

DpageTitle

Attempts:

3 left

💡 Hint

Common Mistakes

Using driver.getTitle() inside assertEquals as expected value is wrong because it fetches actual value.

Comparing actualTitle to itself always passes and misses test failures.

The expectedTitle variable holds the expected value from separated test data. Comparing it to actualTitle verifies correct behavior.

4fill in blank

hard

Fill both blanks to create a data-driven test method signature and annotation.

Selenium Java

@[1](name = "LoginTest", dataProvider = "[2]")
public void testLogin(String username, String password) {

Drag options to blanks, or click blank then click option'

ATest

BDataProvider

CloginData

DBeforeTest

Attempts:

3 left

💡 Hint

Common Mistakes

Using @DataProvider instead of @Test on the test method causes errors.

Using wrong data provider name breaks data binding.

The @Test annotation marks the test method, and loginData is the name of the data provider supplying test data, enabling data separation and coverage.

5fill in blank

hard

Fill all three blanks to define a data provider method returning separated test data.

Selenium Java

public Object[][] [1]() {
    return new Object[][] {
        [2],
        [3]
    };
}

Drag options to blanks, or click blank then click option'

AloginData

B{"user1", "pass1"}

C{"user2", "pass2"}

DtestData

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong method name breaks the link to the test method.

Incorrect data format causes runtime errors.

The method named loginData returns a 2D Object array with separate username and password pairs, enabling data-driven tests and better coverage.