GitHub Actions configuration in Selenium Java - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the name of the GitHub Actions workflow.

Selenium Java

name: [1]

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

Asteps

Brun

Cjobs

DJava Selenium Tests

Attempts:

3 left

💡 Hint

Common Mistakes

Using keywords like 'run' or 'jobs' instead of a name string.

Leaving the name blank.

The name field sets the workflow's name shown in GitHub Actions.

2fill in blank

medium

Complete the code to specify the event that triggers the workflow on every push.

Selenium Java

on: [1]

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

Apush

Bpull_request

Cschedule

Dworkflow_dispatch

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pull_request' when the goal is to trigger on push.

Using 'schedule' which runs on a timer, not on push.

The on field defines the event that triggers the workflow. push triggers it on every push.

3fill in blank

hard

Fix the error in the job definition by completing the job ID.

Selenium Java

jobs:
  [1]:
    runs-on: ubuntu-latest

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

Abuild

Bruns-on

Cname

Dsteps

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'runs-on' as a job ID.

Using 'steps' or 'name' as job ID.

The job ID is a key under jobs. It should be a simple identifier like 'build'.

4fill in blank

hard

Fill both blanks to define a step that checks out the repository code.

Selenium Java

    steps:
      - name: Checkout code
        uses: [1]
        with:
          [2]: 'v3'

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

Aactions/checkout@v3

Bref

Cactions/setup-java@v3

Dversion

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'version' instead of 'ref' in the with block.

Using 'actions/setup-java@v3' instead of checkout action.

The uses field specifies the action to checkout code. The with field uses ref to specify the version.

5fill in blank

hard

Fill all three blanks to define a step that sets up Java 17 and runs Maven tests.

Selenium Java

      - name: Setup Java
        uses: [1]
        with:
          java-version: '[2]'
      - name: Run tests
        run: [3]

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

Aactions/setup-java@v3

B17

Cmvn test

Dactions/checkout@v3

Attempts:

3 left

💡 Hint

Common Mistakes

Using the checkout action instead of setup-java for Java setup.

Using wrong Java version format.

Running wrong command instead of 'mvn test'.

The Java setup uses 'actions/setup-java@v3'. The Java version is '17'. The test command is 'mvn test'.

Practice

1. What is the main purpose of a GitHub Actions workflow file in a Selenium Java project?

easy

A. To store test results permanently on GitHub

B. To write Java code for Selenium tests

C. To automate running Selenium Java tests on code changes

D. To manually trigger tests from the command line

Solution

1. Step 1: Understand the role of GitHub Actions workflow

   The workflow file defines automated steps that run on events like code changes.

2. Step 2: Connect workflow to Selenium Java tests

   It automates running Selenium Java tests whenever code is pushed or a pull request is made.

3. Final Answer:

   To automate running Selenium Java tests on code changes -> Option C

4. Quick Check:

   Workflow automates tests = D [OK]

Hint: Workflows automate tasks on code events like push or PR [OK]

Common Mistakes:

• Confusing workflow with writing test code
• Thinking tests run only manually
• Assuming workflow stores test results

2. Which of the following is the correct syntax to specify the Java version in a GitHub Actions workflow step?

easy

A. java-version: 17

B. uses: actions/setup-java@v3
with:
java-version: '17'

C. run: setup-java --version 17

D. setup-java version=17

Solution

1. Step 1: Identify correct action usage syntax

   The official way to set Java version is using 'uses' with 'actions/setup-java@v3' and 'with' parameters.

2. Step 2: Check the correct parameter name and format

   The parameter is 'java-version' with the version as a string, e.g., '17'.

3. Final Answer:

   uses: actions/setup-java@v3 with: java-version: '17' -> Option B

4. Quick Check:

   Correct action syntax = C [OK]

Hint: Use 'uses' with 'actions/setup-java@v3' and 'java-version' key [OK]

Common Mistakes:

• Using 'run' instead of 'uses' for setup-java
• Missing 'with' keyword
• Incorrect parameter name or format

3. Given this GitHub Actions snippet, what will happen when code is pushed to the main branch?

on:
  push:
    branches:
      - main
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-java@v3
        with:
          java-version: '11'
      - run: mvn test

medium

A. The workflow runs tests using Java 11 on push to main branch

B. The workflow runs tests using Java 17 on any branch push

C. The workflow does not run because 'on' is missing

D. The workflow runs but skips tests

Solution

1. Step 1: Analyze the trigger event

   The workflow triggers on push events to the 'main' branch only.

2. Step 2: Check Java version and test command

   Java 11 is set up, and 'mvn test' runs the tests.

3. Final Answer:

   The workflow runs tests using Java 11 on push to main branch -> Option A

4. Quick Check:

   Push to main triggers tests with Java 11 = B [OK]

Hint: Check 'on' event and Java version in 'setup-java' step [OK]

Common Mistakes:

• Assuming tests run on all branches
• Confusing Java 11 with Java 17
• Ignoring the trigger event

4. Identify the error in this GitHub Actions workflow snippet for running Selenium Java tests:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-java@v3
        with:
          java-version: 11
      - run: mvn clean test

medium

A. java-version should be a string, e.g., '11'

B. Missing 'on' trigger event

C. The 'run' command should be 'mvn test clean'

D. actions/checkout@v3 is deprecated

Solution

1. Step 1: Check the 'java-version' format

   The 'java-version' parameter must be a string, so it should be '11' with quotes.

2. Step 2: Verify other parts

   Though 'on' is missing, the question focuses on the snippet error; 'mvn clean test' is correct; 'actions/checkout@v3' is current.

3. Final Answer:

   java-version should be a string, e.g., '11' -> Option A

4. Quick Check:

   Java version needs quotes = A [OK]

Hint: Always quote Java version in setup-java 'with' block [OK]

Common Mistakes:

• Using number instead of string for java-version
• Confusing order of mvn commands
• Assuming checkout action is outdated

5. You want to run Selenium Java tests on both push and pull request events, but only for the 'develop' and 'release' branches. Which is the correct 'on' configuration in your GitHub Actions workflow?

hard

A. on:
push:
branches: [develop]
pull_request:
branches: [release]

B. on:
push:
branches: [main]
pull_request:
branches: [main]

C. on:
push:
branches-ignore: [develop, release]
pull_request:
branches-ignore: [develop, release]

D. on:
push:
branches: [develop, release]
pull_request:
branches: [develop, release]

Solution

1. Step 1: Understand event triggers for push and pull_request

   You want both push and pull_request events to trigger on 'develop' and 'release' branches.

2. Step 2: Check correct syntax for multiple branches

   Use 'branches' with a list of branch names under both push and pull_request keys.

3. Final Answer:

   on: push: branches: [develop, release] pull_request: branches: [develop, release] -> Option D

4. Quick Check:

   Push and PR on develop, release branches = A [OK]

Hint: List branches under both push and pull_request keys [OK]

Common Mistakes:

• Using branches-ignore instead of branches
• Triggering on wrong branches like main
• Separating branches for push and pull_request incorrectly