I spent the day today making the tests for my project run in parallel. As part of that, I had my first encounter with the SerializeMixin, which you can use in conjunction with the `--parallel` flag to ensure that certain tests don't run at the same time. It's neat, in theory:
https://docs.djangoproject.com/en/3.2/topics/testing/advanced/#enforce-running-test-classes-sequentially One thing I found kind of lacking about it is that it didn't easily solve my main problem. What I wanted to do was to just mark meddlesome tests to run serially. To do that though is kind of tricky. The way I eventually did so was to set lockfile as: lockfile = Path(__file__).parents[1] / "settings.py" I didn't find many others using SerializeMixin online (searching Github and Google), which surprised me, and I didn't see any other solutions like mine when I looked either. It sort of felt like an under-used tool. The way it works now, you use the SerializeMixin in your test class, and then you set up a property on the class called `lockfile`, that points to a file that is used to lock the tests so none others can run at the same time. The docs show an example that has `lockfile = __file__`, which I thought I could just sprinkle into my meddlesome tests to fix them. Unfortunately, that just locks different classes within a single tests.py file, so I had to do the solution above. A couple thougths: 1. Should we tweak the docs to show something like the above, that would make the solution there easier to just drop in? 2. Would it be crazy to upgrade the SerailzeMixin so that if lockfile is left out, it finds some standard file in every django project and uses that for the locking? If it worked that way, switching to parallel tests would just mean using the `--parallel` flag, identifying tests that failed, and mixing in the SerializeMixin into each of those tests. It'd be much easier. Currently if the property is missing, you get a ValueError. Thoughts? Mike -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/70ac0aec-f1a5-4bdb-876d-582e75168820n%40googlegroups.com.
