Something that is untested is broken,  and that is why am writing on Testing flask applications using Pytest , although the origin of this quote is unknown and while it is not entirely correct, it is also not far from the truth. Untested applications make it hard to improve existing code and developers of untested applications tend to become pretty paranoid. If an application has automated tests, you can safely make changes and instantly know if anything breaks.
Flask provides a way to test your application by exposing the Werkzeug test Client and handling the context locals for you. You can then use that with your favourite testing solution.
In this documentation we will use the pytest package as the base framework for our tests. You can install it with pip, like so:

pip install pytest

The Application

First, we need an application to test; we will use the application from the Tutorial. If you don’t have that application yet, get the source code from the examples.

The Testing Skeleton

We begin by adding a tests directory under the application root. Then create a Python file to store our tests ( When we format the filename like test_*.py, it will be auto-discoverable by pytest.
Next, we create a pytest fixture called client() that configures the application for testing and initializes a new database.:

import os
import tempfile
import pytest
from flaskr import flaskr
def client():
    db_fd,['DATABASE'] = tempfile.mkstemp()['TESTING'] = True
    client =
    yield client

This client fixture will be called by each individual test. It gives us a simple interface to the application, where we can trigger test requests to the application. The client will also keep track of cookies for us.
During setup, the TESTING config flag is activated. What this does is disable error catching during request handling, so that you get better error reports when performing test requests against the application.
Because SQLite3 is filesystem-based, we can easily use the tempfile module to create a temporary database and initialize it. Themkstemp() function does two things for us: it returns a low-level file handle and a random file name, the latter we use as database name. We just have to keep the db_fd around so that we can use the os.close() function to close the file.
To delete the database after the test, the fixture closes the file and removes it from the filesystem.
If we now run the test suite, we should see the following output:

$ pytest
================ test session starts ================
rootdir: ./flask/examples/flaskr, inifile: setup.cfg
collected 0 items
=========== no tests ran in 0.07 seconds ============

Even though it did not run any actual tests, we already know that our flaskr application is syntactically valid, otherwise the import would have died with an exception.

ALSO CHECK:  Facebook like emoji rating using Jquery

The First Test

Now it’s time to start testing the functionality of the application. Let’s check that the application shows “No entries here so far” if we access the root of the application (/). To do this, we add a new test function to, like this:

def test_empty_db(client):
    """Start with a blank database."""
    rv = client.get('/')
    assert b'No entries here so far' in

Notice that our test functions begin with the word test; this allows pytest to automatically identify the function as a test to run.
By using client.get we can send an HTTP GET request to the application with the given path. The return value will be a response_class object. We can now use the data attribute to inspect the return value (as string) from the application. In this case, we ensure that 'No entries here so far' is part of the output.
Run it again and you should see one passing test:

$ pytest -v
================ test session starts ================
rootdir: ./flask/examples/flaskr, inifile: setup.cfg
collected 1 items
tests/ PASSED
============= 1 passed in 0.10 seconds ==============

Logging In and Out

The majority of the functionality of our application is only available for the administrative user, so we need a way to log our test client in and out of the application. To do this, we fire some requests to the login and logout pages with the required form data (username and password). And because the login and logout pages redirect, we tell the client to follow_redirects.
Add the following two functions to your file:

def login(client, username, password):
    return'/login', data=dict(
    ), follow_redirects=True)
def logout(client):
    return client.get('/logout', follow_redirects=True)

Now we can easily test that logging in and out works and that it fails with invalid credentials. Add this new test function:

def test_login_logout(client):
    """Make sure login and logout works."""
    rv = login(client,['USERNAME'],['PASSWORD'])
    assert b'You were logged in' in
    rv = logout(client)
    assert b'You were logged out' in
    rv = login(client,['USERNAME'] + 'x',['PASSWORD'])
    assert b'Invalid username' in
    rv = login(client,['USERNAME'],['PASSWORD'] + 'x')
    assert b'Invalid password' in

Test Adding Messages

We should also test that adding messages works. Add a new test function like this:

def test_messages(client):
    """Test that messages work."""
    rv ='/add', data=dict(
        text='<strong>HTML</strong> allowed here'
    ), follow_redirects=True)
    assert b'No entries here so far' not in
    assert b'&lt;Hello&gt;' in
    assert b'<strong>HTML</strong> allowed here' in

Here we check that HTML is allowed in the text but not in the title, which is the intended behavior.
Running that should now give us three passing tests:

$ pytest -v
================ test session starts ================
rootdir: ./flask/examples/flaskr, inifile: setup.cfg
collected 3 items
tests/ PASSED
tests/ PASSED
tests/ PASSED
============= 3 passed in 0.23 seconds ==============

Other Testing Tricks

Besides using the test client as shown above, there is also the test_request_context() method that can be used in combination with the with statement to activate a request context temporarily. With this you can access the requestg and session objects like in view functions.

ALSO CHECK:  The Photo Stick, Your Excellent File Backup Device


I am both a front and backend developer

View all posts

Add comment

Your email address will not be published. Required fields are marked * Protection Status