As it says on the tin: write a cypress spec that tests changes made to Colony's admins.
Testing
It should cover:
Adding a new admin
Pending states for adding a new admin
Confirmed states for adding a new admin
Removing an existing admin
Pending states for removing an existing admin
Confirmed states for removing an existing admin
Admin table list gets updated with the new data (after an admin was added or removed)
Colony Home admin avatars / user info get updated with the new data (after an admin was added or removed)
Best practices
Please note that, as a best practice, prefer to add a new data-test attribute, to hook onto components, rather then relying on elements/class/ids selectors and filtering from there.
Example:
/*
* Component (not the actual one, simplified)
*/
const AvatarDropdown = () => (
<Popover ... >
<button
...
data-test="avatarDropdown"
/>
</Popover>
);
/*
* Test (not the actual one, simplified)
*/
it('Open the Claim Username flow', () => {
...
cy.get('button[data-test="avatarDropdown"]').click();
...
});
As it says on the tin: write a
cypress
spec that tests changes made to Colony's admins.Testing
It should cover:
Best practices
Please note that, as a best practice, prefer to add a new
data-test
attribute, to hook onto components, rather then relying on elements/class/ids selectors and filtering from there.Example:
See this example spec: https://github.com/JoinColony/colonyDapp/blob/master/cypress/integration/claim-username.js
Resources
A couple of resources to help you along you're journey: