pytest-django | A Django plugin for pytest | Plugin library

@hoefling and @Arkadiusz Łukasiewicz were right, I just needed to add the corresponding DB within the factories:

pytest-django doesn't actually find tests in a file called tests.py out of the box. If you want to keep using a file called tests.py you'll need to add a pytest.ini file in your top-level directory:

My tests are not being found. Why?

By default, pytest looks for tests in files named test_*.py (note that this is not the same as test*.py) and *_test.py. If you have your tests in files with other names, they will not be collected. Note that Django’s startapp manage command creates an app_dir/tests.py file. Also, it is common to put tests under app_dir/tests/views.py, etc.

To find those tests, create a pytest.ini file in your project root and add an appropriate python_files line to it:

Using sed:

You cannot just add an alias in the form of

Every block type has a corresponding 'native' data type for the data it expects to work with - for the simpler blocks, this data type is what you'd expect (e.g. a string for CharBlock, an Image instance for ImageChooserBlock) but for a few of the more complex ones, there's a custom type defined:

• for RichTextBlock, the native type is wagtail.core.rich_text.RichText (which behaves similarly to a string, but also has a source property where e.g. page IDs in page links are kept intact)
• for StreamBlock, the native type is wagtail.core.blocks.StreamValue (a sequence type, where each item is a StreamValue with block_type and value properties).

The render method will generally be quite forgiving if you use the wrong types (such as a string for RichTextBlock or a list of dicts for StreamBlock), since it's really just invoking your own template code. The clean method will be more picky, since it's running Python logic specific to each block.

Unfortunately the correct types to use for each block aren't really formally documented, and some of them are quite fiddly to construct (e.g. a StructValue needs to be passed a reference to the corresponding StructBlock) - outside of test code, there isn't much need to create these objects from scratch, because the data will usually be coming from some outside source instead (e.g. a form submission or the database), and each block will be responsible for converting that to its native type.

With that in mind, I'd recommend that you construct your data by piggybacking on the to_python method, which converts the JSON representation as stored in the database (consisting of just simple Python data types - integers, strings, lists, dicts) into the native data types:

so adding this code to conftest.py resolved the problem for me

I never used such integration-testing setup, but I’ve seen it somewhere.

You can run the django-admin testserver mydata.json command to spin up a testing server with data from a provided fixture. The way it was done in the example I saw was by making a custom Django command where instead of static fixture the testserver’s database was populated dynamically by factories. I don’t remember the details how it was implemented, though.

After the testserver was ready, the Cypress tests were run. Backend and the frontend were wired by npm’s start-server-and-test package.

Application with similar setup can be checked out here. Especially note the custom testserver command as well as the cypress commands.

Use prefetch_related

This is a known issue with cpython on windows. The error occurs when black tries to run multiple workers on >60 core machines because the default number of process workers given by os.cpu_count() breaks some other windows limit (number of waiting processes? I'm not quite sure). Black >=19.10b0 has a fix for this, so try updating the version of black in your pre-commit config if you can?

• Python bug report: https://bugs.python.org/issue26903
• Fix applied by this PR in black: https://github.com/psf/black/pull/838