Test client for request simulation in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Flask test client code?

Consider this Flask app and test client code snippet. What will be the printed output?

Flask

from flask import Flask, jsonify
app = Flask(__name__)

@app.route('/hello')
def hello():
    return jsonify(message='Hello, Test!')

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

A null

B {'message': 'hello, test!'}

C {'message': 'Hello, Test!'}

D SyntaxError

💡 Hint

Check what response.json returns when the endpoint returns a JSON response.

The response.json property parses the JSON response body and returns a Python dictionary. The endpoint returns {'message': 'Hello, Test!'}, so that is printed.

❓ state_output

intermediate

What is the status code after this test client POST request?

Given this Flask app and test client POST request, what is the value of response.status_code?

Flask

from flask import Flask, request
app = Flask(__name__)

@app.route('/submit', methods=['POST'])
def submit():
    data = request.json
    if data and 'name' in data:
        return 'Received', 201
    return 'Bad Request', 400

with app.test_client() as client:
    response = client.post('/submit', json={'name': 'Alice'})
    print(response.status_code)

A 200

B 500

C 400

D 201

💡 Hint

Look at the return status code when the JSON contains the 'name' key.

The route returns status code 201 when the JSON contains the 'name' key. The test client sends {'name': 'Alice'}, so the status code is 201.

🔧 Debug

advanced

Why does this Flask test client code raise an error?

Examine this Flask test client code. Why does it raise an error?

Flask

from flask import Flask
app = Flask(__name__)

@app.route('/test')
def test():
    return 'OK'

with app.test_client() as client:
    response = client.post('/test')
    print(response.status_code)

A 405 Method Not Allowed error because '/test' only allows GET by default

B 404 Not Found error because '/test' route does not exist

C 500 Internal Server Error due to missing return statement

D 200 OK because POST works on '/test' route

💡 Hint

Check the allowed HTTP methods for the route.

The route '/test' only allows GET requests by default. Sending a POST request causes a 405 Method Not Allowed error.

📝 Syntax

advanced

Which option correctly simulates a PUT request with JSON data using Flask test client?

Choose the correct code snippet to send a PUT request with JSON data {'id': 1} using Flask's test client.

Flask

from flask import Flask
app = Flask(__name__)

with app.test_client() as client:
    # Choose the correct option to send PUT with JSON
    pass

A client.put('/update', content_type='application/json', data={'id': 1})

B client.put('/update', json={'id': 1})

C client.put('/update', data='{'id': 1}')

D client.put('/update', data={'id': 1})

💡 Hint

Use the test client parameter that automatically serializes JSON.

The json parameter automatically serializes the dictionary and sets the content type. Other options either pass a string incorrectly or pass data without serialization.

🧠 Conceptual

expert

What happens to Flask app context during test client requests?

When using Flask's app.test_client() to simulate requests, which statement about the application context is true?

A Each test client request automatically pushes and pops the app context, so you can access <code>flask.g</code> and <code>current_app</code> inside the request.

B The app context is never pushed during test client requests; you must manually push it to access <code>flask.g</code>.

C The test client disables app context to speed up tests, so <code>flask.g</code> is always null.

D The app context is shared globally and never popped, so test client requests can cause context leaks.

💡 Hint

Think about how Flask manages context during simulated requests.

Flask's test client automatically manages the app context for each request, pushing it before and popping it after, allowing access to flask.g and current_app during the request.