| Commit message (Collapse) | Author | Lines |
|
The subclass will contain assertions that are useful for testing Discord
commands. The currently included assertion tests that a command will
raise a MissingPermissions exception if the author lacks permissions.
|
|
The member and user update listeners should already be detecting and
updating other fields so by the time a user leaves, the rest of the
fields should be up-to-date.
* Dedent condition which was indented too far
|
|
sync() should be called on the UserSyncer.
|
|
sync() should be called on the RoleSyncer.
|
|
A user should be patched only if the name, discriminator, or avatar
changes.
|
|
|
|
Members should not be patched if other attributes have changed.
|
|
Members should be patched if their roles have changed.
|
|
A PUT request should be sent to set in_guild as False and update other
fields.
|
|
A PUT request should be sent if the colour, name, permissions, or
position changes.
|
|
It is obsolete because MockRole now takes care of creating the Colour
and Permissions objects.
|
|
Instances of discord.Colour and discord.Permissions will be created
by default or when ints are given as values for those attributes.
|
|
A DELETE request should be sent.
|
|
A POST request should be sent with the new role's data.
* Add a fixture to create a MockRole
|
|
|
|
|
|
Reduces redundancy in the tests by taking care of the mocks, calling of
the function, and the assertion.
|
|
A PATCH request should be sent. The error should only be raised if it
is not a 404.
* Add a fixture to create ResponseCodeErrors with a specific status
|
|
Roles and users should be synced only if a guild is successfully
retrieved.
|
|
While on 3.7, the CustomMockMixin needs to be leveraged so that
coroutine members are replace with AsyncMocks instead.
|
|
This prevents persistence of changes to the cog instance; sync_guild
would otherwise remain as a mock object for any subsequent tests.
|
|
* Move patches to setUp
|
|
Should instantiate syncers and run a sync for the guild.
|