No bugs found in Mattermost SaaS

QAwerk bugs not found

Mattermost

Mattermost is an open source, fully customizable platform purpose-built for technical and operations teams to facilitate secure collaboration throughout the entire software development lifecycle.

Mattermost serves as a unified platform enabling teams worldwide to enhance their productivity through real-time communication, task and project management, and workflow automation. Its core features encompass integrated team messaging, audio and screen sharing, in-line code syntax highlighting, and more.

Stellar job on the app, Mattermost team! No bugs were discovered during testing!

version tested
3
browsers used
version tested
32
hours spent testing
version tested
>100
test cases run
bugs found
0
bugs found

No bugs found after inviting new members

Precondition:

The user has logged into the app.

Steps to Reproduce:
  1. Click the “Invite Members” button.
  2. Enter a valid email address in the ‘To’ input box.
  3. Click the “Invite” button.
  4. Click the “Join Now” button in the received email.
  5. Make sure that the “Create Your Account” form is displayed.
  6. Enter the username and password for the new member.
  7. Click the “Create Account” button.
Environment:

Windows 10
Firefox v.113.0.1
Google Chrome v. 113.0.5672.127
Microsoft Edge v. 113.0.1774.50

Expected Result:

The member’s account has been created successfully. The new user is now listed as a member in the Sys Admin test members list.

Actual Result:

Bug not found.

No bugs found after inviting new members

No bugs found after sending urgent message to newly created member

Precondition:

The Sys admin has logged into the app.
The new member has been added to the group.

Steps to Reproduce:
  1. Click the “+” button to compose a direct message.
  2. Search for the added member.
  3. Select the member from the list.
  4. Click the “Go” button.
  5. Enter the message.
  6. Set the message priority as “Urgent.”
  7. Enable the “Request Acknowledgement” option.
  8. Send the message.
  9. Log in as the member to read the message.

 

Environment:

Windows 10
Firefox v.113.0.1
Google Chrome v. 113.0.5672.127
Microsoft Edge v. 113.0.1774.50

Expected Result:

An unread message is displayed in the member’s profile. The user is able to read and respond to the message from the Sys Admin. The “Acknowledge” button and “Urgent” priority are both displayed for the member.

Actual Result:

Bug not found.

No bugs found after sending urgent message to newly created member

No bugs found after adding new board using existing template

Precondition:
  1. The user has logged into the app.
  2. An existing channel is opened.
Steps to Reproduce:
  1. Click the “Create a Board” button.
  2. Click the “Use This Template” button.
  3. Update the board name.
Environment:

Windows 10
Firefox v.113.0.1
Google Chrome v. 113.0.5672.127
Microsoft Edge v. 113.0.1774.50

Expected Result:

The new board has been successfully created; the created board is now visible on the “Boards” page; a notification regarding the linked board is displayed in the channel.

Actual Result:

Bug not found.

No bugs found after adding new board using existing template

No bugs found after adding new user group

Precondition:
  1. The user has logged into the app.
  2. There are at least 2 members existing in the workspace.
Steps to Reproduce:
  1. Select the “User Groups” tab.
  2. Click the “Create Group” button.
  3. Enter the group’s name.
  4. Search for existing members.
  5. Click the “Create Group” button.
Environment:

Windows 10
Firefox v.113.0.1
Google Chrome v. 113.0.5672.127
Microsoft Edge v. 113.0.1774.50

Expected Result:

The new user group with the existing members has been successfully created.

Actual Result:

Bug not found.

No bugs found after adding new user group

No bugs found after verifying access to newly created private playbook

Precondition:
  1. The user has logged into the app.
  2. The user is currently on the “Threads” tab.

 

Steps to Reproduce:
  1. Click the “Playbooks” tab located on the right side of the page.
  2. Click the “Create Playbook” button.
  3. Choose the “Private Playbook” option.
  4. Enter the playbook name.
  5. Select a template.
  6. Enter a description for the playbook.
  7. Click the “Create Playbook” button.
  8. Log in as another member and verify access to the newly created playbook.
Environment:

Windows 10
Firefox v.113.0.1
Google Chrome v. 113.0.5672.127
Microsoft Edge v. 113.0.1774.50

Expected Result:

The new private playbook has been successfully created, and other members are unable to view the created playbook.

Actual Result:

Bug not found.

No bugs found after verifying access to newly created private playbook

No bugs found after adding trigger for auto closing task

Precondition:
  1. The user has logged into the app.
  2. A public playbook with an assigned task has been created.
Steps to Reproduce:
  1. Open the existing public playbook.
  2. Switch to the “Tasks” tab.
  3. Click on “Edit” for the existing task.
  4. Click the “Task Actions” button.
  5. In the Trigger section, fill in the “Keyword” and “Posted by” fields.
  6. Turn on the option to “Mark the task as done”.
  7. Click the “Save” button.
Environment:

Windows 10
Firefox v.113.0.1
Google Chrome v. 113.0.5672.127
Microsoft Edge v. 113.0.1774.50

Expected Result:

A new trigger for automatically closing tasks with a specific keyword has been created.

Actual Result:

Bug not found.

No bugs found after adding trigger for auto closing task

No bugs found after moving existing channels to new category

Precondition:

The user has logged into the system.

Steps to Reproduce:
  1. Open the desired existing channel.
  2. Click on the channel’s name and select the “Move to” option from the drop-down list.
  3. Choose the “New Category” option.
  4. Enter the desired Category name.
  5. Click the “Create” button.
Environment:

Windows 10
Firefox v.113.0.1
Google Chrome v. 113.0.5672.127
Microsoft Edge v. 113.0.1774.50

Expected Result:

A new category has been successfully created, and the channel is now displayed within the newly created category.

Actual Result:

Bug not found.

No bugs found after moving existing channels to new category

No bugs found after setting header to channel

Precondition:
  1. The user has logged into the app.
  2. Open any existing channel with at least one member.

 

Steps to Reproduce:
  1. Click on “Add a channel header.”
  2. Enter the desired channel header.
  3. Click the “Save” button.
  4. Log in as the second member of the channel.
  5. Open the test channel.
Environment:

Windows 10
Firefox v.113.0.1
Google Chrome v. 113.0.5672.127
Microsoft Edge v. 113.0.1774.50

Expected Result:

The channel header is now visible to both members of the chat; a notification from the System user is displayed in the channel: “[test user who set the channel header]” has updated the channel header to: “[channel header]”.

Actual Result:

Bug not found.

No bugs found after setting header to channel
No bugs found after setting header to channel

No bugs found after conducting call with member of channel

Precondition:

Two users from the same workspace are currently logged into the application.

Steps to Reproduce:
  1. Open the conversation with the first user.
  2. Click the “Start Call” button.
  3. Open the chat with another user.
  4. Click the “Join Call” button.
Environment:

Windows 10
Firefox v.113.0.1
Google Chrome v. 113.0.5672.127
Microsoft Edge v. 113.0.1774.50

Expected Result:

The call feature works successfully; after finishing the call, both members receive notifications about the call’s duration.

Actual Result:

Bug not found.

No bugs found after conducting call with member of channel

No bugs found after sharing edit permissions for board with new member

Precondition:
  1. User 1 has logged into the app.
  2. At least one board has been created by the user (and only the current user has access to it).
Steps to Reproduce:
  1. Log in as another user (User 2) and attempt to open the test board.
  2. Confirm that the board is not accessible for User 2.
  3. Switch back to User 1 and open the test board.
  4. Click the “Share” button.
  5. Add User 2 to the list as an editor.
  6. Access the board using User 2’s account.
Environment:

Windows 10
Firefox v.113.0.1
Google Chrome v. 113.0.5672.127
Microsoft Edge v. 113.0.1774.50

Expected Result:

User 2 is able to successfully view and edit the created board.

Actual Result:

Bug not found.

Mattermost contains numerous useful features. Throughout testing, I did not encounter any critical issues. The application is user-friendly and exhibits good performance.
Tetiana, QA engineer

Tetiana, QA engineer

No Bugs Found!

No Bugs Found! We tried to find bugs in this product but failed to spot any. While we still believe no software is 100% free of bugs, this app contains no critical or apparent defects that could negatively impact the user experience.

Need a reliable QA partner?

Hire us