| Commit message (Collapse) | Author | Age | Lines |
| |\
| |
| |
| | |
bug/backend/b704/ready-missing-cache
|
| | |\ |
|
| | | |\ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | |\| |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This will prevent child classes to be instantiated unless they implement
all abstract methods, leading to a more descriptive error message.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This will serve as an ABC for tests for individual rules.
The base class provides runners for allowed and disallowed
cases, and the children classes then only provide the cases
and implementations of helper methods specific to each rule.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
The name msg is less descriptive and creates a needless name conflict in local gen exp.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The rule was incorrectly printing out the maximum amount of allowed attachments
instead of the configured interval. This commit also adjusts the rule's unit
test case.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
(hopefully).
|
| | | |/
| |/| |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This error is due to the use of an actual instance of APIClient as the
spec for the mock. recreate() is called in __init__ which in turn
creates a task for the _create_session coroutine.
The approach to the solution is to use the type for the spec rather than
and instance, thus avoiding any call of __init__. However, without an
instance, instance attributes will not be included in the spec.
Therefore, they are defined as class attributes on the actual APIClient
class definition and given default values.
Alternatively, a subclass of APIClient could have been made in the
tests.helpers module to define those class attributes. However, it
seems easier to maintain if the attributes are in the original class
definition.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Should PUT user's data or POST it if the user doesn't exist.
ResponseCodeError should be re-raised if status code isn't a 404.
A helper method was added to reduce code redundancy between the 2 tests.
|
| | | |
| | |
| | |
| | | |
This better ensures that roles are being sorted when patching.
|
| | | |
| | |
| | |
| | |
| | | |
The listener was changed earlier to simply set in_guild to False.
This commit accounts for that in the test.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The sync commands should only run if the author has the administrator
permission.
* Add missing spaces after class docstrings
* Add missing docstring to SyncCogCommandTests
|
| | | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
| | |
| | |
| | | |
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
|