In this lesson, we will explore testing complex API functionalities in the Django REST Framework, specifically filtering, sorting, and pagination. Testing these features ensures that our API behaves as expected when handling various user queries. By the end of this lesson, you will have the knowledge to write comprehensive test cases for these operations and combine them to test more complex scenarios effectively.

Note: In this lesson, we will consider only the basic setup for such tests. If you want to learn more about testing in the Django REST API and how to build stable tests that cover all the required behavior, check out the Advanced Testing for Django REST FRAMEWORKS app course path (coming soon).

Before we start with the new tests, let's briefly recap the setup of our Django project. In previous course, we covered filtering, sorting and pagination for your views. Here's a quick summary of the core components we'll use in this lesson:

We use a fixture stored in myapp/fixtures/todos.json to ensure consistent test data:

We will use a custom filter:

And a custom pagination:

These classes are used in our ListCreateAPI view to ensure it can handle sorting, filtering, and pagination:

Filtering allows users to retrieve specific subsets of data based on certain criteria. In our Todo API, we'll start by testing the completed field.

Let's write a test case to filter Todo items by their completion status:

Reminder: As we have pagination enabled for the todos by default, in all test cases you must use response.data['results'] instead of response.data. This ensures that you are accessing the actual list of todo items within the paginated response.

In the above test case:

• We use the fixtures attribute to load data from todos.json.
• The setUp method initializes the URL for the Todo list endpoint.
• We then have two test methods:
  • test_filter_completed_todos: This tests the filtering of completed Todo items.
  • test_filter_uncompleted_todos: This tests the filtering of uncompleted Todo items.
• For each test, we make a GET request with the appropriate filter parameter and validate the response using assertions. We validate the number of returned items and that all items have a specified value for the field used for filtering.

Running these tests will ensure that our API correctly filters Todo items based on their completion status.

Suggestions for extending this test case:

• Test filtering by other fields like priority, assignee, and group.
• Combine multiple filter parameters in a single request.
• Test the case when no items match the filter criteria.

Sorting allows users to order data based on specific fields. We'll test sorting Todo items by their priority field.

Let's write a test case to sort Todo items by their priority:

In this test case:

• We test the sorting functionality of the Todo list endpoint by the priority field in both ascending and descending order.
• The test_sort_todos_by_priority_asc method validates the ascending sort order.
• The test_sort_todos_by_priority_desc method validates the descending sort order.
• Both methods check that the response status is 200 OK and that the priority values in the response are sorted as expected.

Suggestions for extending this test case:

• Test sorting by other fields like task, completed, and assignee.
• Combine multiple sorting fields in a single request.

Pagination allows users to retrieve data in chunks or pages. We'll test the pagination of Todo items.

Let's write a test case to paginate Todo items:

In this test case:

• We test the pagination functionality of the Todo list endpoint by specifying the page_size and page parameters.
• The test_paginate_todos_first_page method checks the first page of results, ensuring it contains 2 items.
• The test_paginate_todos_second_page method checks the second page of results, ensuring it contains 1 item.
• Both methods verify that the response status is 200 OK and the number of items in the results matches the expected count.

Suggestions for extending this test case:

• Test with different page_size values.
• Test accessing a non-existing page.

Combining filtering, sorting, and pagination allows for more complex queries. We'll test a combination of these operations.

Let's write a test case combining filtering, sorting, and pagination:

In this test case:

• We combine filtering by completed, sorting by priority, and pagination parameters.
• The assertTrue(all(not todo['completed'] for todo in response.data['results'])) line iterates over all items in the response data to check that they all have completed set to False.
• The priorities list is created to hold all priority values from the response, ensuring they are in ascending order. This list is then compared to the sorted version of itself to confirm that the priorities are sorted correctly.

Suggestions for extending this test case:

• Combine different fields for filtering and sorting.
• Test combined operations with varying page_size values.
• Test combinations with more complex filter criteria.
• Filter items in a way that results in 0 items returned.

urlencode is a helpful utility from django.utils.http that transforms a dictionary of parameters into a URL-encoded query string. This is particularly useful when constructing complex URLs with multiple query parameters.

Example:

In the combined test case, using urlencode ensures that the query parameters are correctly formatted for the GET request.

In this lesson, we covered:

• Testing filtering functionality in Django REST Framework.
• Testing sorting functionality.
• Testing pagination functionality.
• Combining filtering, sorting, and pagination operations in test cases.

Each section provided practical examples and explanations to help you understand how to write comprehensive test cases for these functionalities.

As you move on to the practice exercises, remember to apply the concepts learned here. These exercises will solidify your understanding and prepare you for real-world scenarios. Keep practicing to get comfortable with testing complex APIs in Django REST Framework.

Congratulations on completing this lesson! You're well on your way to mastering the art of testing Django APIs. Happy coding!