GitHub Actions integration in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

GitHub Actions Workflow Run Result

You have a GitHub Actions workflow configured to run Selenium tests using Python. The workflow file includes a step to install dependencies and run pytest. What will be the output if the tests fail?

Selenium Python

name: Selenium Tests
on: [push]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Set up Python
        uses: actions/setup-python@v4
        with:
          python-version: '3.12'
      - name: Install dependencies
        run: pip install selenium pytest
      - name: Run tests
        run: pytest tests/

A The workflow run will be marked as failed and the logs will show pytest failure details.

B The workflow run will be marked as successful regardless of test failures.

C The workflow run will be canceled automatically without any logs.

D The workflow run will retry the tests infinitely until they pass.

💡 Hint

Think about how GitHub Actions treats non-zero exit codes from commands.

GitHub Actions marks a job as failed if any command returns a non-zero exit code. Since pytest returns a non-zero exit code on test failures, the workflow run will be marked as failed and logs will show the failure details.

❓ Configuration

intermediate

Correct GitHub Actions Step to Cache Python Dependencies

You want to speed up your Selenium Python tests in GitHub Actions by caching the pip packages. Which step configuration correctly caches the dependencies?

A

- name: Cache pip
  uses: actions/cache@v3
  with:
    path: ~/.cache/pip
    key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
    restore-keys: |
      ${{ runner.os }}-pip-

B

- name: Cache pip
  run: pip cache save ~/.cache/pip

C

- name: Cache pip
  uses: actions/cache@v1
  with:
    path: /usr/local/lib/python3.12/site-packages
    key: pip-cache

D

- name: Cache pip
  uses: actions/cache@v3
  with:
    path: ~/.pip
    key: ${{ runner.os }}-pip-cache

💡 Hint

Look for the official cache action usage and correct cache path for pip.

Option A uses the official actions/cache@v3 action with the correct pip cache directory ~/.cache/pip and a key based on the OS and requirements file hash, which is the recommended way to cache pip dependencies.

🔀 Workflow

advanced

Triggering GitHub Actions Workflow on Pull Request and Push

You want your Selenium Python tests to run automatically on both pull requests and pushes to the main branch. Which on configuration in the workflow file achieves this?

A

on:
  push:
    branches:
      - main
  pull_request:
    branches:
      - develop

B

on:
  push:
    branches:
      - '*'
  pull_request:
    branches:
      - '*'

C

on:
  push:
    branches:
      - develop
  pull_request:
    branches:
      - main

D

on:
  push:
    branches:
      - main
  pull_request:
    branches:
      - main

💡 Hint

Consider which branches should trigger the workflow for both push and pull request events.

Option D correctly triggers the workflow on pushes and pull requests targeting the main branch. Other options either target wrong branches or all branches, which is not the requirement.

❓ Troubleshoot

advanced

Diagnosing Selenium Test Failures in GitHub Actions

Your Selenium tests run fine locally but fail in GitHub Actions with errors related to the browser driver not found. What is the most likely cause?

A The tests are running too fast in GitHub Actions causing timing issues.

B The GitHub Actions runner does not have the browser driver installed or configured in PATH.

C The Selenium version used locally is different from the one in GitHub Actions.

D The GitHub Actions workflow file is missing the <code>actions/checkout</code> step.

💡 Hint

Think about what is needed for Selenium to control a browser in a fresh environment.

Selenium requires a browser driver (like chromedriver) to be installed and accessible in the PATH. GitHub Actions runners do not have these drivers pre-installed by default, so the failure is usually due to missing driver setup.

✅ Best Practice

expert

Best Practice for Securely Storing Browser Driver Versions in GitHub Actions

You want to ensure your Selenium tests use a specific browser driver version in GitHub Actions and keep this version configurable without hardcoding it in the workflow file. What is the best practice?

A Store the browser driver version as a secret in GitHub repository settings and reference it in the workflow using <code>secrets</code>.

B Hardcode the browser driver version directly in the workflow YAML file under the install step.

C Store the browser driver version in a separate configuration file in the repository and read it during the workflow run.

D Use the latest browser driver version always without specifying any version.

💡 Hint

Consider how to keep configuration flexible and visible to the workflow without exposing secrets unnecessarily.

Storing the driver version in a configuration file in the repo allows easy updates and visibility. Secrets are for sensitive data, not version numbers. Hardcoding reduces flexibility. Using latest can cause unexpected failures.