Coverage reporting in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

Understanding coverage report output in Flask testing

You run tests on a Flask app with coverage enabled. The coverage report shows 85% for a specific module. What does this mean?

A 85% of the code lines in that module were executed during tests

B 85% of the functions in that module have no bugs

C 85% of the tests passed successfully for that module

D 85% of the module's code is optimized for performance

💡 Hint

Think about what coverage measures: code execution during tests.

Coverage percentage shows how many lines of code were run during tests. 85% means some lines were not tested.

📝 Syntax

intermediate

Correct command to run coverage for Flask tests

Which command correctly runs Flask tests with coverage reporting using the coverage.py tool?

A coverage run -m pytest tests/

B pytest --coverage tests/

C flask coverage run tests/

D coverage test run tests/

💡 Hint

Remember the syntax for running coverage with pytest.

The correct command is coverage run -m pytest tests/ which runs tests under coverage measurement.

🔧 Debug

advanced

Why does coverage report show 0% for a Flask route?

You wrote a test that calls a Flask route, but coverage shows 0% for that route's code. What is the most likely cause?

A The test calls the route but coverage is not measuring subprocesses

B The route code has a syntax error preventing execution

C Coverage only measures database queries, not route code

D The test does not actually call the route function

💡 Hint

Think about whether the route function is really executed during the test.

If the test does not call the route function, coverage will show 0% because the code never runs.

❓ state_output

advanced

Interpreting coverage HTML report results

After running coverage and generating an HTML report, you see some lines highlighted in red. What does this indicate?

A These lines are optimized and run faster

B These lines contain syntax errors

C These lines were not executed during tests

D These lines are deprecated and should be removed

💡 Hint

Colors in coverage reports show which lines ran or not.

Red lines in coverage HTML reports mean those lines were not run during tests, so they lack coverage.

🧠 Conceptual

expert

Why use coverage reporting in Flask projects?

What is the main benefit of using coverage reporting when testing a Flask application?

A It automatically fixes bugs found in the Flask app

B It shows which parts of the code are tested, helping improve test completeness

C It speeds up the Flask app by optimizing code paths

D It replaces the need for writing unit tests

💡 Hint

Think about what coverage helps developers understand about their tests.

Coverage helps identify untested code so developers can write tests to cover those parts, improving reliability.

Practice

1. What is the main purpose of coverage reporting in a Flask application?

easy

A. To improve the speed of the Flask app

B. To deploy the Flask app to a server

C. To show which parts of the app are tested by your tests

D. To create a user interface for the app

Solution

1. Step 1: Understand coverage reporting

   Coverage reporting tracks which parts of your code are executed during tests.

2. Step 2: Identify its purpose in Flask

   It helps you see which parts of your Flask app have tests and which do not.

3. Final Answer:

   To show which parts of the app are tested by your tests -> Option C

4. Quick Check:

   Coverage reporting = shows tested parts [OK]

Hint: Coverage shows tested code parts, not speed or deployment [OK]

Common Mistakes:

• Confusing coverage with app speed optimization
• Thinking coverage deploys the app
• Assuming coverage creates UI

2. Which command correctly runs tests with coverage in a Flask project?

easy

A. pytest coverage run

B. coverage run -m pytest

C. flask coverage run

D. coverage test run

Solution

1. Step 1: Recall the coverage run syntax

   The correct command to run tests with coverage is 'coverage run -m pytest'.

2. Step 2: Check other options

   Other options mix commands incorrectly or use invalid syntax.

3. Final Answer:

   coverage run -m pytest -> Option B

4. Quick Check:

   Correct coverage test run command = coverage run -m pytest [OK]

Hint: Use 'coverage run -m pytest' to run tests with coverage [OK]

Common Mistakes:

• Swapping order of coverage and pytest
• Using 'flask' command with coverage incorrectly
• Typing 'coverage test run' which is invalid

3. Given you ran coverage run -m pytest successfully, which command shows a text summary of coverage results?

medium

A. coverage report

B. pytest --coverage

C. coverage html

D. flask coverage report

Solution

1. Step 1: Identify commands for coverage output

   'coverage report' shows a text summary in the terminal, while 'coverage html' creates a web page report.

2. Step 2: Eliminate incorrect options

   'pytest --coverage' is not a standard command, and 'flask coverage report' is invalid.

3. Final Answer:

   coverage report -> Option A

4. Quick Check:

   Text summary command = coverage report [OK]

Hint: Use 'coverage report' for text summary, 'coverage html' for web report [OK]

Common Mistakes:

• Confusing 'coverage html' with text output
• Using invalid commands like 'pytest --coverage'
• Trying 'flask coverage report' which doesn't exist

4. You ran coverage run -m pytest but coverage report shows 0% coverage. What is the likely cause?

medium

A. Tests did not execute any Flask app code

B. You forgot to install Flask

C. Coverage report command is misspelled

D. You ran coverage without pytest

Solution

1. Step 1: Understand 0% coverage meaning

   0% coverage means no code was executed during tests, so coverage tool found no lines run.

2. Step 2: Analyze possible causes

   If tests ran but did not call Flask app code, coverage stays zero. Missing Flask or misspelling commands would cause errors, not zero coverage.

3. Final Answer:

   Tests did not execute any Flask app code -> Option A

4. Quick Check:

   0% coverage = no app code run in tests [OK]

Hint: 0% means tests ran but didn't touch app code [OK]

Common Mistakes:

• Assuming 0% means Flask is not installed
• Thinking coverage report command typo causes 0%
• Believing running coverage without pytest causes 0%

5. You want to generate a detailed HTML coverage report for your Flask app after running tests. Which sequence of commands is correct?

hard

A. flask coverage run; coverage html; open html/index.html

B. pytest run coverage; coverage report; open index.html

C. coverage test run; coverage html; open coverage/index.html

D. coverage run -m pytest; coverage html; open htmlcov/index.html

Solution

1. Step 1: Run tests with coverage

   Use 'coverage run -m pytest' to run tests and collect coverage data.

2. Step 2: Generate HTML report and open it

   Run 'coverage html' to create the report in 'htmlcov' folder, then open 'htmlcov/index.html' to view it.

3. Step 3: Verify other options

   Other options use invalid commands or wrong paths for report files.

4. Final Answer:

   coverage run -m pytest; coverage html; open htmlcov/index.html -> Option D

5. Quick Check:

   Run tests, generate HTML, open htmlcov/index.html [OK]

Hint: Run tests, then 'coverage html', then open htmlcov/index.html [OK]

Common Mistakes:

• Using wrong command order or invalid commands
• Opening wrong file path for HTML report
• Confusing 'pytest run coverage' with correct syntax