tests.management.commands package#
Submodules#
tests.management.commands.add_additional_test_data_for_clubs module#
Script to add test data for testing club admin and pre-paid
tests.management.commands.add_test_data module#
Script to create cobalt test data from csv files
CSV Files are processed in sort order and depend upon data that is created in earlier steps. For example, an Event needs to be created before an EventEntry.
File format is:
Row 1 - app, model [, duplicates]
app - name of Django application, e.g. events model - Django model name e.g. EventEntry duplicates - optional literal. If the word duplicates is present then they are allowed
Row 2 - headings
These map to the field names of the table.
Example:
accounts , TeamMate id.user.accounts.User, id.team_mate.accounts.User, make_payments aa , mark , 0 bb , mark , 0
- class tests.management.commands.add_test_data.Command[source]#
Bases:
BaseCommand
- accounts_user(app, model, data)[source]#
Accounts get created first (must be first file) and we keep a reference to them for use when processing the other files
tests.management.commands.add_test_data_forum_posts module#
Script to create cobalt test data
- class tests.management.commands.add_test_data_forum_posts.Command[source]#
Bases:
BaseCommand
- handle(*args, **options)[source]#
The actual logic of the command. Subclasses must implement this method.
tests.management.commands.create_test_users_from_session_file module#
tests.management.commands.mass_email_test module#
tests.management.commands.reformat_test_csvs module#
Reformat test CV files so you can edit them with the content under the titles
tests.management.commands.run_tests_integration module#
tests.management.commands.run_tests_silent module#
tests.management.commands.run_tests_unit module#
tests.management.commands.sanitise_production_data_for_testing module#
Script to sanitise prod data so we can use it for testing