Testing routes and responses in Flask - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a test client for the Flask app.

Flask

with app.[1]() as client:
    response = client.get('/')

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

Arun

Btest_request_context

Ctest_client

Dapp_context

Attempts:

3 left

💡 Hint

Common Mistakes

Using app.run() instead of app.test_client()

Using app.app_context() which is for context, not client

Using test_request_context() which is for context, not client

The test_client() method creates a client to simulate requests to the Flask app for testing.

2fill in blank

medium

Complete the code to check the HTTP status code of the response.

Flask

assert response.[1] == 200

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

Aheaders

Bstatus_code

Ccontent

Ddata

Attempts:

3 left

💡 Hint

Common Mistakes

Checking response.data instead of status_code

Using response.content which is not a Flask attribute

Checking response.headers instead of status_code

The status_code attribute holds the HTTP status code returned by the response.

3fill in blank

hard

Fix the error in the test by completing the code to decode the response data.

Flask

assert response.data.[1]('utf-8') == 'Hello, World!'

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

Adecode

Bsplit

Cencode

Dstrip

Attempts:

3 left

💡 Hint

Common Mistakes

Using encode() which converts string to bytes

Using split() or strip() which do not convert bytes to string

The response data is bytes, so we decode it to a string using decode('utf-8').

4fill in blank

hard

Fill both blanks to test a POST request with JSON data and check the response JSON.

Flask

response = client.post('/submit', json=[1])
assert response.[2]['status'] == 'success'

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

A{'name': 'Alice'}

Bjson

Cdata

D{'status': 'success'}

Attempts:

3 left

💡 Hint

Common Mistakes

Passing JSON as a string instead of a dictionary

Using response.data instead of response.json for JSON response

We send JSON data as a dictionary in the json parameter. The response JSON is accessed via response.json.

5fill in blank

hard

Fill all three blanks to test a route with query parameters and check the response text.

Flask

response = client.get('/search?query=[1]')
assert response.[2] == 200
assert response.data.[3]('utf-8') == 'Results for test'

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

Atest

Bstatus_code

Cdecode

Dquery

Attempts:

3 left

💡 Hint

Common Mistakes

Not decoding response data before comparing

Checking response.data instead of response.status_code for status

Using wrong query parameter value

The query parameter is 'test'. We check status_code for 200. The response data is decoded with decode('utf-8') to compare text.

Practice

1. What is the main purpose of using app.test_client() in Flask testing?

easy

A. To create a database connection for testing

B. To start the Flask server for manual testing

C. To simulate HTTP requests to routes without running the server

D. To generate HTML templates automatically

Solution

1. Step 1: Understand the role of app.test_client()

   This method creates a client that can send HTTP requests to the Flask app internally without needing the server to run.

2. Step 2: Compare with other options

   Starting the server or creating a database connection are unrelated to test_client(). It does not generate templates either.

3. Final Answer:

   To simulate HTTP requests to routes without running the server -> Option C

4. Quick Check:

   app.test_client() simulates requests [OK]

Hint: Remember test_client() simulates requests internally [OK]

Common Mistakes:

• Thinking test_client() starts the server
• Confusing test_client() with database setup
• Assuming it generates HTML templates

2. Which of the following is the correct way to test a GET request to the '/' route using Flask's test client?

easy

A. response = client.post('/')

B. response = client.get('/')

C. response = client.request('PUT', '/')

D. response = client.fetch('/')

Solution

1. Step 1: Identify the HTTP method for the route

   The question asks for a GET request, so the method should be get().

2. Step 2: Match the method with the test client syntax

   Flask test client uses client.get(path) to send GET requests. Other methods like post() or request('PUT', ...) are for different HTTP verbs.

3. Final Answer:

   response = client.get('/') -> Option B

4. Quick Check:

   GET request uses client.get() [OK]

Hint: Use client.get() for GET requests in tests [OK]

Common Mistakes:

• Using post() instead of get() for GET requests
• Using client.fetch() which does not exist
• Confusing HTTP methods in test calls

3. Given this Flask test code:

with app.test_client() as client:
    response = client.get('/hello')
    print(response.status_code)
    print(response.data.decode())

If the '/hello' route returns 'Hello, World!' with status 200, what will be printed?

medium

A. 200
Hello, World!

B. 404
Not Found

C. 500
Internal Server Error

D. 200
b'Hello, World!'

Solution

1. Step 1: Understand the route response

   The route '/hello' returns the string 'Hello, World!' with HTTP status 200.

2. Step 2: Analyze the test output

   The response.status_code will be 200. The response.data is bytes, so decoding it with decode() converts it to the string 'Hello, World!'.

3. Final Answer:

   200 Hello, World! -> Option A

4. Quick Check:

   Status 200 and decoded response text [OK]

Hint: Decode response.data to get string content [OK]

Common Mistakes:

• Not decoding response.data (shows bytes)
• Expecting 404 or 500 status codes incorrectly
• Confusing status_code with response content

4. What is wrong with this Flask test code snippet?

client = app.test_client()
response = client.get('/missing')
assert response.status_code == 200

Assuming '/missing' route does not exist.

medium

A. The status code will be 404, so the assertion fails

B. The get method should be post for missing routes

C. The test client must be used inside a context manager

D. The response object does not have status_code attribute

Solution

1. Step 1: Check the route existence

   The route '/missing' does not exist, so Flask returns a 404 Not Found status.

2. Step 2: Evaluate the assertion

   The assertion expects status code 200, but the actual is 404, causing the test to fail.

3. Final Answer:

   The status code will be 404, so the assertion fails -> Option A

4. Quick Check:

   Missing route returns 404, assertion expects 200 [OK]

Hint: Check route exists before asserting status 200 [OK]

Common Mistakes:

• Assuming missing routes return 200
• Thinking get() must be post() for missing routes
• Believing status_code attribute is missing

5. You want to test a Flask route that returns JSON data {"success": true, "count": 5} with status 201. Which test code correctly verifies both the status and JSON content?

hard

A. response = client.get('/data')
assert response.status_code == 201
assert response.json() == {"success": True, "count": 5}

B. response = client.get('/data')
assert response.status_code == 200
assert response.json == {"success": True, "count": 5}

C. response = client.post('/data')
assert response.status_code == 200
assert response.get_json() == {"success": True, "count": 5}

D. response = client.get('/data')
assert response.status_code == 201
assert response.get_json() == {"success": True, "count": 5}

Solution

1. Step 1: Check HTTP method and status code

   The route returns status 201, so the test must assert response.status_code == 201. The method is GET as per the question.

2. Step 2: Verify JSON content correctly

   Flask test response uses get_json() to parse JSON data. Using response.json is incorrect in Flask.

3. Final Answer:

   response = client.get('/data') assert response.status_code == 201 assert response.get_json() == {"success": True, "count": 5} -> Option D

4. Quick Check:

   Use get_json() and check status 201 [OK]

Hint: Use get_json() to check JSON response content [OK]

Common Mistakes:

• Using response.json instead of get_json()
• Checking wrong status code (200 instead of 201)
• Using POST instead of GET method