Coverage reporting in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run tests with coverage in Django.

Django

coverage run --source='.' manage.py [1]

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

Atest

Brunserver

Cmigrate

Dshell

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'runserver' instead of 'test' will start the server, not run tests.

Using 'migrate' runs database migrations, not tests.

Use test to run Django tests with coverage.

2fill in blank

medium

Complete the command to generate a coverage report in the terminal.

Django

coverage [1]

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

Arun

Berase

Creport

Dhtml

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'run' again instead of 'report' will rerun tests.

Using 'html' generates a report in a browser, not terminal.

The report command shows coverage results in the terminal.

3fill in blank

hard

Fix the error in the command to generate an HTML coverage report.

Django

coverage [1] -d coverage_html

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

Acombine

Breport

Crun

Dhtml

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'report' outputs text, not HTML files.

Using 'run' reruns tests, not generate reports.

The html command generates an HTML report in the specified directory.

4fill in blank

hard

Fill both blanks to create a coverage report that omits tests folder and shows missing lines.

Django

coverage report --omit=[1] --[2]

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

Atests/*

Bhtml

Cshow-missing

Dxml

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'html' or 'xml' instead of 'show-missing' will change report format.

Not omitting tests folder will include test code in coverage.

Use --omit=tests/* to skip test files and --show-missing to list uncovered lines.

5fill in blank

hard

Fill all three blanks to run tests with coverage, generate HTML report, and erase old data.

Django

coverage [1] && coverage [2] --source='.' manage.py test && coverage [3] -d htmlcov

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

Arun

Berase

Chtml

Dreport

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'run' in the first blank will combine old data with new.

Skipping 'erase' may cause outdated coverage info.

First erase old data, then run tests with run, finally generate HTML report with html.

Practice

1. What is the main purpose of coverage reporting in Django testing?

easy

A. To deploy the Django app to a server

B. To speed up the test execution

C. To automatically fix bugs in the code

D. To show which parts of your code are tested

Solution

1. Step 1: Understand coverage reporting

   Coverage reporting tracks which lines of code are executed during tests.

2. Step 2: Identify the main goal

   The goal is to see which parts of the code are covered by tests to improve test quality.

3. Final Answer:

   To show which parts of your code are tested -> Option D

4. Quick Check:

   Coverage shows tested code = A [OK]

Hint: Coverage shows tested code parts clearly [OK]

Common Mistakes:

• Thinking coverage speeds up tests
• Believing coverage fixes bugs automatically
• Confusing coverage with deployment

2. Which command correctly runs Django tests with coverage collection?

easy

A. coverage test manage.py run

B. python manage.py coverage test

C. coverage run manage.py test

D. manage.py coverage run test

Solution

1. Step 1: Recall the correct coverage command syntax

   The coverage tool runs the test command with: coverage run manage.py test

2. Step 2: Compare options

   Only coverage run manage.py test matches the correct syntax; others mix command order incorrectly.

3. Final Answer:

   coverage run manage.py test -> Option C

4. Quick Check:

   Correct coverage test command = A [OK]

Hint: Use 'coverage run' before 'manage.py test' [OK]

Common Mistakes:

• Swapping command order
• Using 'coverage test' instead of 'coverage run'
• Adding 'coverage' after manage.py

3. After running coverage run manage.py test, what command shows a summary of coverage results in the terminal?

medium

A. coverage report

B. coverage summary

C. coverage show

D. coverage list

Solution

1. Step 1: Identify the command for coverage summary

   The command to display coverage results in the terminal is 'coverage report'.

2. Step 2: Eliminate incorrect options

   Commands like 'coverage summary', 'coverage show', and 'coverage list' do not exist or do not show coverage summary.

3. Final Answer:

   coverage report -> Option A

4. Quick Check:

   Terminal coverage summary = coverage report = C [OK]

Hint: Use 'coverage report' to see terminal summary [OK]

Common Mistakes:

• Using non-existent commands like 'coverage summary'
• Confusing 'coverage html' with terminal report
• Trying 'coverage show' which is invalid

4. You ran coverage run manage.py test but coverage report shows 0% coverage. What is the likely cause?

medium

A. Coverage data file was deleted before report

B. Tests did not execute any code

C. Coverage was run without the test command

D. Coverage report command is misspelled

Solution

1. Step 1: Understand why coverage shows 0%

   If coverage data file is missing or deleted, report shows 0% coverage.

2. Step 2: Check other options

   Tests running but no coverage data means data file issue; misspelling report command causes error, not 0%.

3. Final Answer:

   Coverage data file was deleted before report -> Option A

4. Quick Check:

   Missing data file = 0% coverage = B [OK]

Hint: Check if .coverage file exists before report [OK]

Common Mistakes:

• Assuming tests never ran
• Thinking coverage run without test causes 0%
• Misspelling report causes error, not zero coverage

5. You want a detailed HTML report of your Django test coverage. Which sequence of commands should you run?

hard

A. coverage report && coverage run manage.py test

B. coverage run manage.py test && coverage html

C. coverage html && coverage run manage.py test

D. manage.py test coverage run && coverage report

Solution

1. Step 1: Run tests with coverage collection

   Use 'coverage run manage.py test' to collect coverage data while running tests.

2. Step 2: Generate HTML report

   Run 'coverage html' after tests to create a detailed HTML coverage report.

3. Step 3: Verify command order

   coverage run manage.py test && coverage html correctly chains these commands; others have wrong order or commands.

4. Final Answer:

   coverage run manage.py test && coverage html -> Option B

5. Quick Check:

   Run tests then html report = D [OK]

Hint: Run tests first, then 'coverage html' for report [OK]

Common Mistakes:

• Running 'coverage html' before tests
• Mixing command order
• Using 'manage.py test coverage run' which is invalid