thunderbird_accounts.mail.tests.test_tasks
Classes
|
|
|
|
|
Pins the Keycloak role grant that opens the gated browser flow for a provisioned user. |
|
|
|
|
- class thunderbird_accounts.mail.tests.test_tasks.TaskTestCase(methodName='runTest')[source]
Bases:
TestCase
- class thunderbird_accounts.mail.tests.test_tasks.UpdateQuotaOnStalwartAccountTestCase(methodName='runTest')[source]
Bases:
TaskTestCase
- class thunderbird_accounts.mail.tests.test_tasks.PublishHostedDkimDNSRecordsTestCase(methodName='runTest')[source]
Bases:
TaskTestCase
- class thunderbird_accounts.mail.tests.test_tasks.DeleteHostedDkimDNSRecordsTestCase(methodName='runTest')[source]
Bases:
TaskTestCase
- class thunderbird_accounts.mail.tests.test_tasks.GrantMailAccessRoleTestCase(methodName='runTest')[source]
Bases:
TaskTestCasePins the Keycloak role grant that opens the gated browser flow for a provisioned user.
- class thunderbird_accounts.mail.tests.test_tasks.CreateStalwartAccountTestCase(methodName='runTest')[source]
Bases:
TaskTestCase- test_success_with_existing_account_and_email(grant_role_mock)
In case they have the reference to the stalwart account, but no actual data on stalwart’s end, we need to make sure the stalwart account was created correctly, and the account and emails weren’t modified outside of expectations.
- test_fail_if_account_lookup_raises_unexpected_error(grant_role_mock)
If get_account blows up with something other than AccountNotFoundError we should fail the task rather than continuing on and risk creating a duplicate account.