Doc'd writing integration tests for the system check framework. #17406
+66
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From DjangoConUS 2023 sprints 🏃. I didn't create a ticket in the issue tracker for this.
This PR adds additional examples to the system checks framework testing section of the documentation to demonstrate how one can test the integration of a system check within a project.
Non-model field system checks must be registered/imported in
apps.py
or__init__.py
in order to function. Testing check functions directly as unit tests doesn't capture this, whereas usingcall_command
does.I added an example of how to assert against checks which raise a
SystemCheckError
as well as one which outputs to stderr, and how to capture the message usingStringIO
.Thanks @evildmp for the crash course on Sphinx links 😄