Running PyTest in GitHub Actions - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

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

PyTest

name: [1]

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

ARun PyTest

BTest Workflow

CCI Pipeline

DPyTest Runner

Attempts:

3 left

💡 Hint

Common Mistakes

Leaving the name empty or using unclear names.

Using special characters that might cause YAML errors.

The name field sets the workflow's name shown in GitHub Actions UI. "Test Workflow" is a clear descriptive name.

2fill in blank

medium

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

PyTest

on: [1]

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

Apush

Bpull_request

Crelease

Dschedule

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pull_request' when you want to run on push.

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

The push event triggers the workflow whenever code is pushed to the repository.

3fill in blank

hard

Fix the error in the job definition to specify the runner environment.

PyTest

jobs:
  test:
    runs-on: [1]

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

Awindows-latest

Bdocker-latest

Cmacos-latest

Dubuntu-latest

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'docker-latest' which is not a valid runner label.

Choosing Windows or macOS runners unnecessarily.

ubuntu-latest is the most common runner for Python testing in GitHub Actions.

4fill in blank

hard

Fill both blanks to install Python and dependencies before running tests.

PyTest

steps:
  - uses: actions/checkout@v3
  - name: Set up Python
    uses: [1]@v4
    with:
      python-version: [2]

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

Aactions/setup-python

B3.12

Cactions/setup-node

D2.7

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'actions/setup-node' instead of Python setup.

Specifying an outdated Python version like 2.7.

Use actions/setup-python@v4 to set up Python, specifying version 3.12 for modern features.

5fill in blank

hard

Fill all three blanks to run PyTest and save test results.

PyTest

  - name: Install dependencies
    run: pip install -r [1]
  - name: Run tests
    run: [2] --junitxml=[3]

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

Arequirements.txt

Bpytest

Ctest-results.xml

Dsetup.py

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'setup.py' instead of 'requirements.txt' for dependencies.

Forgetting to specify the test results file.

Install dependencies from requirements.txt, run pytest, and save results to test-results.xml.

Practice

1. What is the main purpose of running pytest in a GitHub Actions workflow?

easy

A. To automatically test code changes and catch errors early

B. To deploy the application to production

C. To create a backup of the repository

D. To format the code automatically

Solution

1. Step 1: Understand pytest's role in GitHub Actions CI

   PyTest is a testing tool that checks if code works correctly. GitHub Actions runs tests automatically on code changes to catch errors early.

2. Final Answer:

   To automatically test code changes and catch errors early -> Option A

3. Quick Check:

   PyTest in GitHub Actions = automatic testing [OK]

Hint: PyTest in GitHub Actions runs tests automatically [OK]

Common Mistakes:

• Confusing testing with deployment
• Thinking PyTest formats code
• Assuming it creates backups

2. Which of the following is the correct step to install PyTest in a GitHub Actions workflow YAML file?

easy

A. run: apt-get install pytest

B. run: npm install pytest

C. run: pip install pytest

D. run: brew install pytest

Solution

1. Step 1: Identify the package manager and correct install command for PyTest

   PyTest is a Python package installed using pip. The correct command is run: pip install pytest.

2. Final Answer:

   run: pip install pytest -> Option C

3. Quick Check:

   Python packages use pip install [OK]

Hint: Use pip to install Python packages like PyTest [OK]

Common Mistakes:

• Using npm which is for JavaScript
• Using apt-get or brew which are system package managers
• Missing the pip command

3. Given this GitHub Actions step in a workflow YAML file:

  - name: Run tests
    run: pytest tests/

What will happen when this step runs?

medium

A. PyTest will deploy the tests to a server

B. PyTest will install dependencies before running tests

C. PyTest will create a test report file automatically

D. PyTest will run all tests inside the tests/ directory

Solution

1. Step 1: Analyze the pytest tests/ command and default behavior

   pytest tests/ runs all test files inside the tests/ folder by default but does not install dependencies or deploy code.

2. Final Answer:

   PyTest will run all tests inside the tests/ directory -> Option D

3. Quick Check:

   pytest tests/ runs tests in tests/ folder [OK]

Hint: pytest <folder> runs tests in that folder [OK]

Common Mistakes:

• Thinking PyTest installs dependencies
• Assuming PyTest deploys code
• Expecting automatic report file creation

4. You wrote this GitHub Actions step:

- name: Run tests
  run: py.test

But the workflow fails with "command not found" error. What is the likely cause?

medium

A. The command should be pytest not py.test

B. PyTest is not installed before running the tests

C. The tests directory is missing

D. GitHub Actions does not support running tests

Solution

1. Step 1: Diagnose the command not found error for py.test

   PyTest must be installed first; both pytest and py.test work if installed.

2. Final Answer:

   PyTest is not installed before running the tests -> Option B

3. Quick Check:

   Install PyTest before running tests [OK]

Hint: Always install PyTest before running it in workflow [OK]

Common Mistakes:

• Assuming command spelling is wrong
• Ignoring PyTest installation step
• Blaming GitHub Actions for test failures

5. You want to create a GitHub Actions workflow that runs PyTest on Python 3.10 and 3.11 versions. Which YAML snippet correctly sets up the Python versions and runs PyTest?

hard

A. jobs:
test:
runs-on: ubuntu-latest
strategy:
matrix:
python-version: [3.10, 3.11]
steps:
- uses: actions/checkout@v3
- name: Set up Python
uses: actions/setup-python@v4
with:
python-version: ${{ matrix.python-version }}
- name: Install dependencies
run: pip install pytest
- name: Run tests
run: pytest

B. jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Set up Python
uses: actions/setup-python@v4
with:
python-version: 3.10
- name: Install dependencies
run: pip install pytest
- name: Run tests
run: pytest
- name: Set up Python
uses: actions/setup-python@v4
with:
python-version: 3.11
- name: Run tests
run: pytest

C. jobs:
test:
runs-on: ubuntu-latest
strategy:
matrix:
python-version: [3.10, 3.11]
steps:
- uses: actions/checkout@v3
- name: Install dependencies
run: pip install pytest
- name: Set up Python
uses: actions/setup-python@v4
with:
python-version: ${{ matrix.python-version }}
- name: Run tests
run: pytest

D. jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Set up Python
uses: actions/setup-python@v4
with:
python-version: 3.10
- name: Run tests
run: pytest

Solution

1. Step 1: Identify YAML with matrix strategy and correct step order for multi-version testing

   Use strategy.matrix to run on 3.10/3.11; checkout, then setup Python with ${{ matrix.python-version }}, install pytest, run tests.

2. Final Answer:

   YAML snippet with matrix strategy and correct step order -> Option A

3. Quick Check:

   Matrix + setup-python + install + run = jobs: test: runs-on: ubuntu-latest strategy: matrix: python-version: [3.10, 3.11] steps: - uses: actions/checkout@v3 - name: Set up Python uses: actions/setup-python@v4 with: python-version: ${{ matrix.python-version }} - name: Install dependencies run: pip install pytest - name: Run tests run: pytest [OK]

Hint: Use matrix for versions, setup-python before install and test [OK]

Common Mistakes:

• Not using matrix for multiple versions
• Installing PyTest before setting Python version
• Repeating setup-python steps instead of matrix