Why CI integration enables continuous testing in Selenium Java - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a Selenium WebDriver for Chrome.

Selenium Java

WebDriver driver = new [1]();

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

AFirefoxDriver

BChromeDriver

CEdgeDriver

DSafariDriver

Attempts:

3 left

💡 Hint

Common Mistakes

Using FirefoxDriver when ChromeDriver is needed.

Forgetting to import the correct driver class.

The ChromeDriver is used to start a Chrome browser session in Selenium.

2fill in blank

medium

Complete the code to assert the page title is 'Home Page' after loading.

Selenium Java

assertEquals("Home Page", driver.[1]());

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

AgetTitle

BgetCurrentUrl

CgetPageSource

DgetWindowHandle

Attempts:

3 left

💡 Hint

Common Mistakes

Using getCurrentUrl() which returns the URL, not the title.

Using getPageSource() which returns the HTML source.

The getTitle() method returns the page title, which we compare to 'Home Page'.

3fill in blank

hard

Fix the error in the test annotation to enable JUnit 5 test execution.

Selenium Java

@[1]
public void testLogin() {
    // test code
}

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

AAfterAll

BBeforeEach

CTest

DTestMethod

Attempts:

3 left

💡 Hint

Common Mistakes

Using '@TestMethod' which is not a valid JUnit 5 annotation.

Confusing test annotations with setup or teardown annotations.

The correct JUnit 5 annotation to mark a test method is @Test.

4fill in blank

hard

Fill both blanks to wait up to 10 seconds for an element with id 'submit' to be clickable.

Selenium Java

WebDriverWait wait = new WebDriverWait(driver, Duration.[1](10));
wait.until(ExpectedConditions.[2](By.id("submit")));

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

AofSeconds

BvisibilityOfElementLocated

CelementToBeClickable

DofMinutes

Attempts:

3 left

💡 Hint

Common Mistakes

Using ofMinutes instead of ofSeconds for duration.

Using visibilityOfElementLocated which waits only for visibility.

Duration.ofSeconds(10) sets a 10-second wait, and elementToBeClickable waits for the element to be clickable.

5fill in blank

hard

Fill all three blanks to create a map of test names to their pass status, filtering only passed tests.

Selenium Java

Map<String, Boolean> passedTests = testResults.entrySet().stream()
    .filter(e -> e.getValue() [1] true)
    .collect(Collectors.toMap(e -> e.getKey(), e -> e.getValue() [2] true));

System.out.println(passedTests.[3]());

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

A==

Csize

Dequals

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'equals' to compare primitive booleans.

Using 'count()' instead of 'size()' on a Map.

The filter uses == true to check boolean values, the map keeps the value as is, and size() prints the count of passed tests.

Practice

1. What is the main benefit of integrating Continuous Integration (CI) with automated testing?

easy

A. Developers write tests manually after each release

B. Tests run automatically on every code change to catch bugs early

C. Tests are only run once before the final product launch

D. CI integration slows down the development process

Solution

1. Step 1: Understand CI integration purpose

   CI integration automates running tests whenever code changes are made.

2. Step 2: Identify the benefit of automation

   This automation helps find bugs early and reduces manual testing effort.

3. Final Answer:

   Tests run automatically on every code change to catch bugs early -> Option B

4. Quick Check:

   CI automation = early bug detection [OK]

Hint: CI runs tests on every change to catch bugs fast [OK]

Common Mistakes:

• Thinking tests run only at the end
• Believing CI slows development
• Assuming manual testing is always needed

2. Which of the following is the correct way to trigger a Selenium test in a CI pipeline using Java?

easy

A. Manually open the browser and run tests

B. Use java -jar selenium-server.jar without test classes

C. Run the test class with mvn test command

D. Write tests in Python and run with python test.py

Solution

1. Step 1: Identify standard Java test execution in CI

   Maven command mvn test runs Java Selenium tests automatically.

2. Step 2: Eliminate incorrect options

   Manual browser opening is not automated; running selenium-server alone doesn't run tests; Python command is unrelated to Java tests.

3. Final Answer:

   Run the test class with mvn test command -> Option C

4. Quick Check:

   Java tests run with mvn test [OK]

Hint: Use mvn test to run Java Selenium tests in CI [OK]

Common Mistakes:

• Confusing manual and automated test runs
• Using wrong commands for Java tests
• Mixing languages in CI commands

3. Given the following CI pipeline snippet triggering Selenium tests, what will happen if a test fails?

stage('Test') {
  steps {
    sh 'mvn test'
  }
}

medium

A. The pipeline will stop and mark the build as failed

B. The pipeline will ignore the failure and continue

C. The tests will rerun automatically until they pass

D. The pipeline will skip the test stage entirely

Solution

1. Step 1: Understand Maven test behavior in CI

   If any test fails, mvn test returns a failure exit code.

2. Step 2: Effect on CI pipeline

   CI pipelines stop on failure exit codes and mark the build as failed to alert developers.

3. Final Answer:

   The pipeline will stop and mark the build as failed -> Option A

4. Quick Check:

   Test failure = pipeline failure [OK]

Hint: Failed tests stop CI build immediately [OK]

Common Mistakes:

• Assuming tests auto-retry on failure
• Thinking pipeline ignores test failures
• Believing tests run without stopping pipeline

4. You integrated Selenium tests in your CI pipeline, but tests are not running after code commits. What is the most likely cause?

medium

A. The Selenium WebDriver is outdated but tests still run

B. Tests are passing too quickly to be noticed

C. The code commits are not triggering any build

D. The test stage is missing or not configured in the CI pipeline

Solution

1. Step 1: Check CI pipeline configuration

   If the test stage is missing or misconfigured, tests won't run after commits.

2. Step 2: Rule out other causes

   Passing tests still run; outdated WebDriver causes failures, not silence; commits usually trigger builds unless disabled.

3. Final Answer:

   The test stage is missing or not configured in the CI pipeline -> Option D

4. Quick Check:

   Missing test stage = no tests run [OK]

Hint: Verify test stage exists in CI config [OK]

Common Mistakes:

• Ignoring pipeline config errors
• Assuming tests run without pipeline setup
• Blaming WebDriver without errors

5. How does integrating Selenium tests into a CI pipeline improve software delivery speed and quality?

hard

A. By running tests automatically on every commit, catching bugs early and reducing manual testing delays

B. By requiring developers to manually trigger tests after each feature is complete

C. By running tests only once before the final release to save time

D. By replacing all manual testing with automated tests without human review

Solution

1. Step 1: Understand CI and Selenium test integration

   Automated tests run on every commit, providing quick feedback on code quality.

2. Step 2: Benefits of early bug detection and automation

   This reduces delays from manual testing and prevents bugs from reaching production.

3. Final Answer:

   By running tests automatically on every commit, catching bugs early and reducing manual testing delays -> Option A

4. Quick Check:

   Auto tests + early bugs = faster, better delivery [OK]

Hint: Auto tests on commits catch bugs early, speeding delivery [OK]

Common Mistakes:

• Thinking tests run only at release
• Believing manual triggers are needed
• Assuming automation removes all human checks