Test Plan - Channel Moderation Settings
Document Version | Description | Date |
v0.1 | Test Plan before team review | Mar 2, 2020 |
v0.2 | Added tests based on initial run on PR | Mar 11, 2020 |
v0.3 | Added tests for Channel Mentions Permission Schemes | Mar 12, 2020 |
v0.4 | Added tests for Permissions Migration | Mar 23, 2020 |
v1.0 | Tested on 5.22 Build | Mar 26, 2020 |
Table of Content
Summary
This document describes the test plan to test the functionality of the Channel Moderation Settings feature which is scheduled for Mattermost v5.22 release.
For the practicality of running tests easily, test cases may follow steps from the preceding test case.
When images exist in parallel to assist with the test case, they are placed right below the corresponding test cases.
Scope
This document outlines the tests for Channel Moderation Settings - UI and Functionality features including system console, chat facing and mobile app changes.
Glossary
Channel Page
Can be accessed from System Console > User Management > Channels page
System Scheme
Can be accessed from System Console > User Management > Permissions page.
Team Override Schemes
Can be accessed from System Console > User Management > Permissions page.
Guests
A user who is marked as Guest
Members
A regular user who does not have system admin, team admin or channel administrator privileges
Assumptions
The tests in this test plans are written with the assumption that:
Testing done on System Console pages is done as a System Administrator, unless otherwise specified by the test case.
Testing is primarily done on the webapp and desktop app, with spot checks on RN mobile app or mobile web browser app to ensure the feature is working fine.
Setup
The following setup will be necessary in order to begin testing:
A Mattermost server and webapp with the latest changes from the 5.22 release branch.
At least one user with system administrator access to the Mattermost instance
At least one user with member access to the Mattermost instance
At least one user with guest access to the Mattermost instance
Log in to Mattermost as a system administrator.
Verify that Mattermost Version 5.22 is running.
Go to the main menu
Go to “About Mattermost”
Mattermost version appears on the About modal
Test Cases
Create Posts
Create Post option for Guests
Login as sysadmin and visit the Channels page and click on a channel.
Uncheck the Create Posts option for Guests and save.
Login as a Guest user and visit the same channel.
Check if the Guest user has the permission to create a post on that channel.
Guest user should not have the permission to create a post on a channel when the option is removed.
As a sysadmin, check the option to allow Create Posts for Guests and save.
Check if the Guest user has the permission to create a post on that channel.
Guest user should have the permission to create a post on a channel when the option is allowed.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Create Post option for Members
Login as sysadmin and visit the Channels page and click on a channel.
Uncheck the Create Posts option for Members and save.
Note: The option to create posts for Guests should still be allowed.
Login as a Regular Member and visit the same channel.
Check if the user has the permission to create a post on that channel.
a. Member should not have the permission to create a post on a channel when the option is removed.As a sysadmin, check the option to allow Create Posts for Members and save.
Check if the user has the permission to create a post on that channel.
a. Member should have the permission to create a post on a channel when the option is allowed.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Post Reactions
Post Reactions option for Guests
Login as sysadmin and visit the Channels page and click on a channel.
Uncheck the Post Reactions option for Guests and save.
Login as a Guest user and visit the same channel.
Check if the Guest user has the permission to react to their posts or to any other posts in the channel.
a. Guest user should not have the permission to react to any post on a channel when the option is removed.As a sysadmin, check the option to allow Post Reactions for Guests and save.
Check if the Guest user has the permission to react to their posts or to any other posts in the channel.
a. Guest user should have the permission to react to any post on a channel when the option is allowed.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Post Reactions option for Members
Login as sysadmin and visit the Channels page and click on a channel.
Uncheck the Post Reactions option for Members and save.
Note: The option to react posts for Guests should still be allowed.
Login as a Regular Member and visit the same channel.
Check if the user has the permission to react to their posts or to any other posts in the channel.
a. Member user should not have the permission to react to any post on a channel when the option is removed.As a sysadmin, check the option to allow Post Reactions for Members and save.
Check if the user has the permission to react to their posts or to any other posts in the channel.
a. Member user should have the permission to react to any post on a channel when the option is allowed.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Post Reactions option removed for Guests & Members in System Scheme
Login as sysadmin and visit the Permissions page in the system console.
Edit the System Scheme and remove the Post Reaction option for Guests & Save.
Visit the Channels page and click on a channel.
Note that the option to allow Post Reactions to a Guest user should be disabled. A message should be displayed indicating the same.
a. Post Reaction option should be disabled for a Guest User. A message Post reactions for guests are disabled in the System Scheme should be displayed.Similarly remove the Post Reaction option for Members in System Scheme & Save.
The option to allow Post Reactions to a Member should be disabled. A message should be displayed indicating the same.
a. Post Reaction option should be disabled for a Members. A message Post reactions for guests & members are disabled in the System Scheme should be displayed.Login as a Guest User and visit the same channel.
Check if the user has the permission to react to their posts or to any other posts in the channel.
a. Guest User should not have the permission to react to any post on any channel when the option is removed from the System Scheme.Login as a Regular Member and visit the same channel.
Check if the user has the permission to react to their posts or to any other posts in the channel.
a. Member should not have the permission to react to any post on any channel when the option is removed from the System Scheme.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Post Reactions option removed for Guests & Members in Team Override Scheme
Login as sysadmin and visit the Permissions page in the system console.
Add a New Team Override Scheme and remove the Post Reaction option for Guests & Save.
Visit the Channels page and click on a channel for which the Team Override scheme was applied.
Note that the option to allow Post Reactions to a Guest user should be disabled. A message should be displayed indicating the same.
a. Post Reaction option should be disabled for a Guest User. A message Post reactions for guests are disabled in the Team Override Scheme should be displayed.Similarly remove the Post Reaction option for Members in Team Override Scheme & Save.
The option to allow Post Reactions to a Member should be disabled. A message should be displayed indicating the same.
a. Post Reaction option should be disabled for a Members. A message Post reactions for guests & members are disabled in the Team Override Scheme should be displayed.Login as a Guest User and visit any channel in the team (mentioned in step 2).
Check if the user has the permission to react to their posts or to any other posts in the channel.
a. Guest User should not have the permission to react to any post on any channel in that team when the option is removed from the Team Override Scheme.Login as a Regular Member and visit any channel in the team (mentioned in step 2).
Check if the user has the permission to react to their posts or to any other posts in the channel.
a. Member should not have the permission to react to any post on any channel in that team when the option is removed from the Team Override Scheme.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass Note: Known issue - MM-23197: There is no provisioning for editing Guest Permissions at Team Override Scheme level Closed |
Manage Members
No option to Manage Members for Guests
Login as sysadmin and visit the Channels page and click on a channel.
Check if there is an option to allow Manage Members for Guests.
a. Option to Manage Members should not be provided for Guest Users.Login as a Guest user and visit the same channel.
Check if the Guest user has the permission to add or remove people in the channel.
a. Guest user should not have the permission to add or remove people on any channel.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Manage Members option for Members
Login as sysadmin and visit the Channels page and click on a channel.
Uncheck the option to Manage Members for Members and save.
Login as a Regular Member and visit the same channel.
Check if the user has the permission to add or remove people in the channel.
a. Member user should not have the permission to add or remove people on a channel when the option is removed.As a sysadmin, check the option to Manage Members for Members and save.
Check if the member now has the permission to add or remove people in the channel.
a. Member user should have the permission to add or remove people on a channel when the option is allowed.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Manage Members option removed for Members in System Scheme
Login as sysadmin and visit the Permissions page in the system console.
Edit the System Scheme and remove the Manage Members option for Members & Save.
Visit the Channels page and click on a channel.
Note that the option to allow Manage Members to a Member should be disabled. A message should be displayed indicating the same.
a. Manage Members option should be disabled for a Members. A message Manage members for members are disabled in the System Scheme should be displayed.Login as a Regular Member and visit any channel.
Check if the user has the permission to invite or remove people in the channel.
a. Member should not have the permission to add or remove people from any channel when the option is removed from the System Scheme.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Manage Members option removed for Members in Team Override Scheme
Login as sysadmin and visit the Permissions page in the system console.
Add a New Team Override Scheme and remove the Manage Members option for Members & Save.
Visit the Channels page and click on a channel for which the Team Override scheme was applied.
The option to allow Manage Members should be disabled. A message should be displayed indicating the same.
a. The option to Manage Members should be disabled for Members. A message Manage Members for members are disabled in the Team Override Scheme should be displayed.Login as a Regular Member and visit any channel in the team (mentioned in step 2).
Check if the user has the permission to add or remove people in the channel.
a. Member should not have the permission to add or remove people on any channel in that team when the option is removed from the Team Override Scheme.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Channel Mentions
Channel Mentions option for Guests
Login as sysadmin and visit the Channels page and click on a channel.
Uncheck the Channel Mentions option for Guests and save.
Login as a Guest user and visit the same channel.
Check if the Guest user has the permission to use special channel mentions like @all, @channel, @here in the channel.
a. Guest user should not have the permission to use special channel mentions like @all, @channel, @here in the channel when the option is removed.As a sysadmin, check the option to allow Channel Mentions option for Guests and save.
Check if the Guest user has the permission to use special channel mentions like @all, @channel, @here in the channel.
a. Guest user should have the permission to use special channel mentions like @all, @channel, @here in the channel when the option is allowed.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Channel Mentions option for Members
Login as sysadmin and visit the Channels page and click on a channel.
Uncheck the Channel Mentions option for Members and save.
Note: The option to use Channel Mentions for Guests should still be allowed.
Login as a Regular Member and visit the same channel.
Check if the user has the permission to use special channel mentions like @all, @channel, @here in the channel.
a. Member user should not have the permission to use special channel mentions like @all, @channel, @here in the channel when the option is removed.As a sysadmin, check the option to allow Channel Mentions for Members and save.
Check if the user has the permission to use special channel mentions like @all, @channel, @here in the channel.
a. Member user should have the permission to use special channel mentions like @all, @channel, @here in the channel when the option is allowed.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Channel Mentions option removed for Guests & Members in System Scheme
Login as sysadmin and visit the Permissions page in the system console.
Edit the System Scheme and remove the option to use Channel Mentions for Guests & Members & Save.
Visit the Channels page and click on a channel.
Note that the option to allow Channel Mentions to a Guest & Member should be disabled. A message should be displayed indicating the same.
a. Channel Mentions option should be disabled for Guests & Members. A message Channel Mentions for guests & members are disabled in the System Scheme should be displayed.Login as a Regular Member and visit any channel.
Check if the user has the permission to use special channel mentions like @all, @channel, @here in the channel.
a. Member should not have the permission to use special channel mentions like @all, @channel, @here from any channel when the option is removed from the System Scheme.Login as a Guest User and visit any channel.
Check if the user has the permission to use special channel mentions like @all, @channel, @here in the channel.
a. Guest User should not have the permission to use special channel mentions like @all, @channel, @here when the option is removed from the System Scheme.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Channel Mentions option removed for Guests & Members in Team Override Scheme
Login as sysadmin and visit the Permissions page in the system console.
Add a New Team Override Scheme and remove the Channel Mentions option for Members & Save.
Visit the Channels page and click on a channel for which the Team Override scheme was applied.
The option to allow Channel Mentions should be disabled for Members. A message should be displayed indicating the same.
a. The option to allow Channel Mentions should be disabled for Members. A message Channel Mentions for members are disabled in the Team Override Scheme should be displayed.Login as a Regular Member and visit any channel in the team (mentioned in step 2).
Check if the user has the permission to use special channel mentions like @all, @channel, @here in the channel.
a. Member should not have the permission to use special channel mentions like @all, @channel, @here on any channel in that team when the option is removed from the Team Override Scheme.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass Note: Known issue - MM-23197: There is no provisioning for editing Guest Permissions at Team Override Scheme level Closed |
Channel Mentions option removed when Create Post is disabled
Login as sysadmin and visit the Channels page and click on a channel.
Uncheck the Create Posts option for Guests.
The option to allow Channel Mentions for Guests should also be disabled. A message should be displayed indicating the same.
a. Option to allow Channel Mentions for Guests should also be disabled when Create Post option is disabled. A message Guests can not use channel mentions without the ability to create posts should be displayed.Uncheck the Create Posts option for Members.
The option to allow Channel Mentions for Members should also be disabled. A message should be displayed indicating the same.
a. Option to allow Channel Mentions for Members should also be disabled when Create Post option is disabled. A message Members can not use channel mentions without the ability to create posts should be displayed.If both Guests & Members are disabled, then the message should read like:
Guests & Members can not use channel mentions without the ability to create posts
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Message when user without channel mention permission uses special channel mentions
Login as sysadmin and visit the Channels page and click on a channel.
Uncheck the Channel Mentions option for Members and save.
Login as a Regular Member and visit the same channel.
Type @ and check if @all, @channel and @here special mentions is not displayed.
Type the following messages:
testing1 @all
testing2 @here
testing3 @channel
a. No other users should get notified. The user should get a system message like this:
Channel notifications are disabled in {{ChannelName}}. The {{Mention}} did not trigger any notifications.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Confirm sending notifications while using special channel mentions
Login as sysadmin and visit the Channels page and click on a channel.
Uncheck the Channel Mentions option for Members and save.
Visit System Console > Site Configuration > Notifications page and ensure the optionShow @channel and @all confirmation dialog: is set to True.
Login as a Regular Member and visit the same channel. Ensure that channel has more than 10 users.
Type the following messages:
testing1 @all
testing2 @here
testing3 @channel
a. User should not receive any confirmation prompt like this while submitting the post:
Confirm sending notifications to entire channel.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Use Special Channel mentions in Channel Header & Channel Purpose
Login as sysadmin and visit the Channels page and click on a channel.
Uncheck the Channel Mentions option for Members and save.
Login as a Regular Member and visit the same channel.
Edit the Channel Header and Channel Purpose as follows:
testing1 @all
testing2 @channelCheck if the special mentions like @all or @channel gets highlighted in the system message
a. Special mentions like @all, @channel should not get highlighted in the system message displayed when Channel Header or Channel Purpose was modified.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Higher Scoped Scheme
Effect of changing System Schemes on a Channel for which Channel Moderation Settings was modified
Login as sysadmin and visit the Channels page and click on a channel.
Uncheck the option to Manage Members for Members and save.
Check the option to Manage Members for Members and save.
Edit the System Scheme and remove the option to use Manage Members for Members & Save.
Visit the Channels page and click on the same channel (as used in step 2).
Check if the option to allow Manage Members for Members should be disabled.
a. Hence the option to allow Manage Members for Members should also be disabled in Channel Moderation Settings when changed in System Scheme.Login as a Regular Member and visit the same channel.
Check if the user has the permission to add or remove people in the channel.
Any changes to System Scheme should also be propagated down to Channel Moderation Settings for individual channels.
a. Regular Member should not be able to add or remove people in the channel when its removed from the System Scheme.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Effect of changing System Schemes on a Channel for which Channel Moderation Settings was never modified
Login as sysadmin and Edit the System Scheme and remove the option to use Manage Members for Members & Save.
Visit the Channels page and click on a channel (which was not modified before).
Check if the option to allow Manage Members for Members should be disabled.
a. Hence the option to allow Manage Members for Members should also be disabled in Channel Moderation Settings when changed in System Scheme.Login as a Regular Member and visit the same channel.
Check if the user has the permission to add or remove people in the channel.
Any changes to System Scheme should also be propagated down to Channel Moderation Settings for individual channels.Regular Member should not be able to add or remove people in the channel when its removed from the System Scheme.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Effect of changing Team Override Schemes on a Channel for which Channel Moderation Settings was never modified
Login as sysadmin & Add a new Team Override Scheme for a team and remove the option to use Manage Members for Members & Save.
Visit the Channels page and click on a channel (belonging to a team used in step 1).
Check if the option to allow Manage Members for Members should be disabled.
Login as a Regular Member and visit the same channel.
Check if the user has the permission to add or remove people in the channel.
Any changes to the Team Override Scheme should also be propagated down to Channel Moderation Settings for individual channels.
a. Hence the option to allow Manage Members for Members should also be disabled in Channel Moderation Settings when changed in Team Override Scheme.Regular Member should not be able to add or remove people in the channel when its removed from the Team Override Scheme.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Effect of changing Team Override Schemes on a Channel for which Channel Moderation Settings was modified
Login as sysadmin and visit the Channels page and click on a channel.
Uncheck the option to Manage Members for Members and save.
Check the option to Manage Members for Members and save.
Add a new Team Override Scheme for the same team (as used in step 2) and remove the option to use Manage Members for Members & Save.
Visit the Channels page and click on the same channel (as used in step 2).
Check if the option to allow Manage Members for Members should be disabled.
Any changes to the Team Override Scheme should also be propagated down to Channel Moderation Settings for individual channels.
a. Hence the option to allow Manage Members for Members should also be disabled in Channel Moderation Settings when changed in Team Override Scheme.Login as a Regular Member and visit the same channel.
Check if the user has the permission to add or remove people in the channel.
a. Regular Member should not be able to add or remove people in the channel when its removed from the Team Override Scheme.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Manage Members removed for Public Channels
Login as sysadmin and create a new Team Override Scheme for a team and remove the option to Manage Members for Public Channels for All Members.
Ensure option to Manage Members for Private Channels is still allowed for All Members.
Visit a Public Channel and check the Channel Moderation Settings.
a. The option to Manage Members for Members should be disabled and unchecked. A message indicating that Manage Members are disabled in the Team Override Scheme should be displayed.Visit a Private Channel and check the Channel Moderation Settings
a. The option to Manage Members for Members for Private Channel should be enabled and checked.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Manage Members removed for Private Channels
Login as sysadmin and create a new Team Override Scheme for a team and remove the option to Manage Members for Private Channels for All Members.
Ensure option to Manage Members for Public Channels is still allowed for All Members.
Visit a Public Channel and check the Channel Moderation Settings.
a. The option to Manage Members for Members for Public Channel should be enabled and checked.Visit a Private Channel and check the Channel Moderation Settings
a. The option to Manage Members for Members for Private Channels should be disabled and unchecked. A message indicating that Manage Members are disabled in the Team Override Scheme should be displayed.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Permissions inherited when channel converted from Public to Private
Login as sysadmin and create a new Team Override Scheme for a team and remove the option to Manage Members for Private Channels for All Members.
Ensure option to Manage Members for Public Channels is still allowed for All Members.
Visit a Public Channel and check the Channel Moderation Settings.
Convert the channel to Private Channel and now check the Moderation Settings.
a. When a channel is converted from Public to Private (or vice versa), the permissions should be inherited from it's higher scoped and should be updated immediately. Hence if a public channel is converted to private channel, the Manage Members option should be disabled and unchecked and a message indicating Manage Members for members are disabled in Team Scheme should be displayed.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Check if user is allowed to Edit or Delete their own posts on a Read-Only channel
Login as a regular member and visit a Channel and submit some posts.
Login as a sysadmin and remove the Create Posts option for Members in Channel Moderation Settings.
As a regular member, user is not able to submit any new posts.
Check if user is able to Edit or Delete any of their previous posts.
a. User should still be able to see the Edit or Delete options on any of their own posts
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Channel Moderation Settings should not be applied for Channel Admins
Login as a sysadmin and remove some permissions on Channel Moderation Settings for a Member like remove following permissions for Members:
Create Posts, Post Reactions, Manage Members, Channel MentionsLogin as a Channel Admin and check if user is still able to create post, use reactions, add or remove people from the channel, use special channel mentions like @all, @channel and @here
Channel Admins should still be able to create post, use reactions, add or remove people from the channel, use special channel mentions like @all, @channel and @here
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Channel Moderation Settings should not be applied for Team Admins
Login as a sysadmin and remove some permissions on Channel Moderation Settings for a Member like remove following permissions for Members:
Create Posts, Post Reactions, Manage Members, Channel MentionsLogin as a Team Admin and check if user is still able to create post, use reactions, add or remove people from the channel, use special channel mentions like @all, @channel and @here
Team Admins should still be able to create post, use reactions, add or remove people from the channel, use special channel mentions like @all, @channel and @here
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Channel Mentions - Permissions Scheme
Channel Mentions System Scheme
Login as a sysadmin and visit Permissions Page.
Click on the System Scheme and Edit Scheme. Click on the Reset to Defaults option and check the default permissions for Channel Mentions
a. By default, Channel Mentions should be enabled for All Members, Channel Admins, Team Admins and System Admins.Remove the Channel Mentions permission for All Members and save. Reload the page and check the values
a. Channel mentions permission should be removed for All Members, but should still be present for Channel Admins and Team Admins.Remove the Channel Mentions permission for Channel Admins and Team Admins and save. Reload the page and check the values.
a. Channel mentions permission should be removed for All Members, Channel Admins and Team Admins.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Channel Mentions Team Override Scheme
Login as a sysadmin and visit Permissions Page.
Click on the System Scheme and Edit Scheme.
Remove the Channel Mentions permission for All Members, Channel Admins and save.
Go to Permissions page and click on Add New Team Override Scheme. Check the values.
a. Channel mentions permission should be removed for All Members and Channel Admins but should still be present for Team Admins.Enable the Channel Mentions permissions for Channel Admins and save. Reload the page and check the values.
a. Channel mentions permission should be removed for All Members, but should be enabled for Channel Admins and Team Admins.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Channel Mentions - All Members
Login as a sysadmin and visit Permissions Page.
Click on the System Scheme and Edit Scheme. Click on the Reset to Defaults option and check the default permissions for Channel Mentions
Remove the Channel Mentions permission for All Members and save.
Login as a regular member and try to use the channel mentions like @all, @channel or @here
a. User should not be able to see the channel mentions like @all, @channel and @here in the autcomplete dropdown when user types @.Submit a post with one of the channel mentions, i.e @all and check if all users in the channel gets notified.
a. If a user submits a post, the user should receive a system message indicating that the channel mentions are disabled and no other user in the channel should get notified.Login as Channel Admin and check if the user is able to use the channel mentions. Similarly login as Team Admin and System Admin and check if user is able to use the channel mentions.
a. Channel Admin, Team Admin and System Admin should still be able to use channel mentions.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Channel Mentions - Channel Admins
Login as a sysadmin and visit Permissions Page.
Click on the System Scheme and Edit Scheme. Click on the Reset to Defaults option and check the default permissions for Channel Mentions
Remove the Channel Mentions permission for All Members and save.
Create a new Team Override Scheme, select a Team and remove the channel mentions permission for Channel Admins and save.
Login as a channel admin and try to use the channel mentions like @all, @channel or @here
a. Channel Admin user should not be able to see the channel mentions like @all, @channel and @here in the autocomplete dropdown when user types @.Submit a post with one of the channel mentions, i.e @all and check if all users in the channel gets notified.
a. If a user submits a post, the user should receive a system message indicating that the channel mentions are disabled and no other user in the channel should get notified.Login as Team Admin and System Admin and check if user is able to use the channel mentions.
a. Team Admin and System Admin should still be able to use channel mentions.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Channel Mentions - Team Admins
Login as a sysadmin and visit Permissions Page.
Click on the System Scheme and Edit Scheme. Click on the Reset to Defaults option and check the default permissions for Channel Mentions
Remove the Channel Mentions permission for All Members and save.
Create a new Team Override Scheme, select a Team and remove the channel mentions permission for Channel Admins and Team Admin and save.
Login as a Team admin and try to use the channel mentions like @all, @channel or @here
a. Team Admin user should not be able to see the channel mentions like @all, @channel and @here in the autocomplete dropdown when user types @.Submit a post with one of the channel mentions, i.e @all and check if all users in the channel gets notified.
a. If a user submits a post, the user should receive a system message indicating that the channel mentions are disabled and no other user in the channel should get notified.Login as System Admin and check if user is able to use the channel mentions.
a. System Admin should still be able to use channel mentions.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |
Permissions Migration
Verify System Scheme & Team Scheme Permission Migration
Following tests were executed to verify the System Scheme & Team Scheme Permission Migration. Here is the glossary of the matrix mentioned below:
Members - Allowed
Enable the permission for all the members for the specified action. For example: Enable Post Reactions in Team Scheme.
Members - Not Allowed
Remove the permission for all the members for the specified action. For example: Remove the Manage Members for a Private Channel in Team Scheme.
C.A - Allowed
Enable the permission for the Channel Admins for the specified action. For example: Enable Manage Members for a Public Channel in Team Scheme.
C.A - Not Allowed
Remove the permission for the Channel Admins for the specified action. For example: Remove the Manage Members for a Public Channel in Team Scheme.
T.A - Allowed
Enable the permission for the Team Admins for the specified action. For example: Enable Manage Members for a Public Channel in Team Scheme.
T.A - Not Allowed
Remove the permission for the Team Admins for the specified action. For example: Remove the Manage Members for a Public Channel in Team Scheme.
Expected Results
The expectations was that the permission retained after the migration, i.e. if a user was allowed a certain action before the migration, the user still continues to has the permission to perform the action after the migration. Similarly if a user did not have permission before the migration, then the user should not have the permission after the migration.
Setup | Results |
Tester: @Rohitesh Gupta (Deactivated) Test Server: postgres.test Build Hash: release-5.22.54.51c83cf Date: 26 March, 2020 | Pass |