Issue #4481
Updated by bmbouter about 5 years ago
I think it's typical to go into an area of the tests (functional or unit) and run your test runner of choice, e.g. <code>py.test</code>. So for example to run "these tests":https://github.com/pulp/pulp/tree/master/pulpcore/tests/unit I would:
1. activate the pulp3 virtualenv with pulplift using <code>workon pulp</code>
2. cd to pulpcore/tests/unit
3. Run with <code>py.test</code>
I get a whole bunch of errors saying <code>Model class pulpcore.app.models.content.Artifact doesn't declare an explicit app_label and isn't in an application in INSTALLED_APPS.</code>
Note that running the py.test on the functional tests works, so this is a unit test issue.
h2. Workaround
You can use <code>manage.py</code> instead to workaround it. I'm hoping we can get py.test working again somehow also.
.