Running the tests¶
Run these tests from the project dts_test_project, it comes prepacked with the correct settings file and extra apps to enable tests to ensure different apps can exist in SHARED_APPS and TENANT_APPS.
Django Custom Test Runner Download
A test runner is a class defining a runtests method. Django ships with a DiscoverRunner class that defines the default Django testing behavior. Hopkins and allen arms company serial numbers. This class defines the runtests entry point, plus a selection of other methods that are used by runtests. Django 2.2 documentation. Django.test.runner; Getting help FAQ Try the FAQ — it's got answers to many common questions. Index, Module Index, or Table of Contents Handy when looking for specific information. Django-users mailing list Search for information in the archives of the django-users mailing list, or post a question.
If you want to run with custom migration executor then do
You can also run the tests with docker-compose
Updating your app’s tests to work with django_tenants¶
Because django will not create tenants for you during your tests, we have packed some custom test cases and other utilities. Zscaler mac download. If you want a test to happen at any of the tenant’s domain, you can use the test case TenantTestCase. It will automatically create a tenant for you, set the connection’s schema to tenant’s schema and make it available at self.tenant. We have also included a TenantRequestFactory and a TenantClient so that your requests will all take place at the tenant’s domain automatically. Here’s an example
Additional information¶
You may have other fields on your tenant or domain model which are required fields.If you have there are two routines to look at setup_tenant and setup_domain
You can also change the test domain name and the test schema name by using get_test_schema_name and get_test_tenant_domain.by default the domain name is tenant.test.com and the schema name is test.
Django Custom Test Runners
You can set the the verbosity by overriding the get_verbosity method.
Running tests faster¶
Using the TenantTestCase can make running your tests really slow quite early in your project. This is due to the fact that it drops, recreates the test schema and runs migrations for every TenantTestCase you have. If you want to gain speed, there’s a FastTenantTestCase where the test schema will be created and migrations ran only one time. The gain in speed is noticiable but be aware that by using this you will be perpertraiting state between your test cases, please make sure your they wont be affected by this.
Running tests using TenantTestCase can start being a bottleneck once the number of tests grow. If you do not care that the state between tests is kept, an alternative is to use the class FastTenantTestCase. Unlike TenantTestCase, the test schema and its migrations will only be created and ran once. This is a significant improvement in speed coming at the cost of shared state.
There are some extra method that you can use for FastTenantTestCase. They are.
flush_data default is True which means is will empty the table after each run. False will keep the data
Django Test Case
How to meet lebanese guys. use_existing_tenant Gets run if the setup doesn’t need to create a new databaseuse_new_tenant Get run is an new database is created