Bugs‌ ‌found‌ ‌in‌ Сlubhouse SaaS: ‌QAwerk‌ ‌Bug‌ ‌Crawl‌

Clubhouse

Clubhouse SaaS is a task management platform that covers every aspect of projects. This SaaS platform allows users to build, write, and integrate various solutions to enhance their business operations. With Clubhouse, companies can build software based on a flexible roadmap that is generated quarterly.

Also, Clubhouse SaaS allows seamless cooperation across multiple departments in a company. You can also integrate Slack, Dropbox, Google Drive, and Github to the Clubhouse platform.

To access Clubhouse.io’s full range of features, you must have an active subscription. New users can also utilize the platform for a free trial period.

Here is a detailed report from our QA team after crawling the SaaS service for bugs.

The ‘User management’ link redirects to a non-existent page

Severity:

Major

Steps to Reproduce:
  1. Go to https://clubhouse.io/ and click on the ‘Pricing’ tab.
  2. Scroll down to the ‘Billing FAQs’ section.
  3. Click the first question: “What can I do in Clubhouse…”.
  4. Click the ‘User management’ link.
Environment:

MacBook Pro 15” 2016, macOS Big Sur 11.1, Google Chrome 88.0.4324.96

Actual Result:

The user is redirected to the “Oops…” page.

Expected Result:

The ‘User management’ page opens.

The ‘Help Center’ link redirects to a non-existent page

Severity:

Major

Precondition:

The user is logged in to the platform.

Steps to Reproduce:
  1. Click the user’s icon and choose the ‘Settings’ option.
  2. Click the ‘Workflows’ button.
  3. Click the ‘Help Center’ hyperlink.
Environment:

MacBook Pro 15” 2016, macOS Big Sur 11.1, Google Chrome 88.0.4324.96

Actual Result:

The ‘Help Center’ link redirects to the “Oops…” page.

Expected Result:

The ‘Help Center’ page exists and opens.

The ‘Upload Icon’ button is cropped

Severity:

Minor

Precondition:

The user is logged in to the platform.

Steps to Reproduce:
  1. Click the user’s icon and choose the ‘Settings’ option.
  2. Click ‘Your Profile’.
  3. Scroll down to the ‘Upload Icon’ button.
Environment:

MacBook Pro 15” 2016, macOS Big Sur 11.1, Google Chrome 88.0.4324.96

Actual Result:

The ‘Upload Icon’ button is cropped.

Expected Result:

The ‘Upload Icon’ button is fully visible.

The ‘Save Changes’ button is available before changes

Severity:

Minor

Precondition:

The user is logged in to the platform.

Steps to Reproduce:
  1. Click the user’s icon and choose the ‘Settings’ option.
  2. Click ‘Your Profile’.
  3. Check the ‘Save Changes’ button.
Environment:

MacBook Pro 15” 2016, macOS Big Sur 11.1, Google Chrome 88.0.4324.96

Actual Result:

The ‘Save Changes’ button is available before the user makes any changes.

Expected Result:

The ‘Save Changes’ button is disabled until the user changes something.

System popups are visible to users

Severity:

Minor

Precondition:

The user is logged in to the platform.

Steps to Reproduce:
  1. Click the user’s icon and choose the ‘Settings’ option.
  2. Click ‘Linked Accounts’.
  3. Click the ‘Link to your account’ button and close the modal.
Environment:

MacBook Pro 15” 2016, macOS Big Sur 11.1, Google Chrome 88.0.4324.96

Actual Result:

The “popup_closed_by_user” message appears.

Expected Result:

The user doesn’t see the system popups.

Incorrect redirection after account deletion

Severity:

Minor

Precondition:

The user is logged in to the platform.

Steps to Reproduce:
  1. Click the user’s icon and choose the ‘Settings’ option.
  2. Click ‘Delete Account’.
  3. Click ‘Delete me’ > Enter a username and confirm.
  4. Open the new email and check the message inside it.
  5. Click ‘Reactivate your account’.
Environment:

MacBook Pro 15” 2016, macOS Big Sur 11.1, Google Chrome 88.0.4324.96

Actual Result:

The account is deactivated. Impossible to log in. The user has to sign up again.

Expected Result:

The user is redirected to the ‘Sign-up’ page directly.

Flawed sign-up validation procedure

Severity:

Minor

Precondition:

The user is logged in to the platform.

Steps to Reproduce:
  1. Click the user’s icon and choose the ‘Settings’ option.
  2. Click ‘Invite New Users’.
  3. Select the ‘Invite by link’ option and send a link to user B.
  4. User B opens a link and fills the form with invalid data.
Environment:

MacBook Pro 15” 2016, macOS Big Sur 11.1, Google Chrome 88.0.4324.96

Actual Result:

Input hints don’t match text field content.

Expected Result:

Input hints match the content in the text field.

Flawed sign-up validation procedure

The ‘Create a story’ button is clickable by Observers

Severity:

Minor

Precondition:

The users are logged in to the platform and have a workspace. User A is the Owner; user B is a Member.

Steps to Reproduce:
  1. User A clicks the user’s icon and chooses the ‘Settings’ option.
  2. Clicks ‘User Directory’ > ‘Active users’ tab.
  3. Click the ‘Member’ input attached to user B.
  4. Set an ‘Observer’ role for user B.
  5. User B reloads the Stories tab and sets the cursor on the green ‘Create a story’ button.
Environment:

MacBook Pro 15” 2016, macOS Big Sur 11.1, Google Chrome 88.0.4324.96

Actual Result:

The green ‘Create a story’ button stays active. The same button on the left top is disabled.

Expected Result:

The ‘Create a story’ button is disabled for the Observers.

The label doesn’t update after page reloading

Severity:

Minor

Precondition:

The user is logged in to the platform and has a workspace with labels and stories.

Steps to Reproduce:
  1. Open the ‘Stories’ tab and add a label to 1 or more stories.
  2. Move these stories to ‘In Progress’ or ‘Completed’ stages.
  3. Click ‘More’ > ‘Labels’ and check the label placeholder.
  4. Reload the page and recheck the placeholder.
Environment:

MacBook Pro 15” 2016, macOS Big Sur 11.1, Google Chrome 88.0.4324.96

Actual Result:

The placeholder doesn’t update after the first page reloads. The user needs to reload the page again to see the valid information.

Expected Result:

The label has the correct data after the first check.

The ‘Get in touch’ form has a flawed validation procedure

Severity:

Minor

Steps to Reproduce:
  1. Go to https://clubhouse.io/ and set the cursor on ‘Switch now’.
  2. Choose ‘Import from Jira’.
  3. Scroll down to the ‘Get in touch’ link.
  4. Click the link and fill the form with invalid data.
  5. Click ‘Submit’ to send the form.
Environment:

MacBook Pro 15” 2016, macOS Big Sur 11.1, Google Chrome 88.0.4324.96

Actual Result:

All fields except the work email and number of seats needed can contain only whitespaces.

Expected Result:

The form validation protocol is stronger and helps salespeople receive valid user data.

Clubhouse is a project management platform for software development that brings everyone on every team together to build better products. This service is well-designed with amazing features and works perfectly. However, there are some minor bugs like broken links and result-action inconsistencies. A lot of forms don't have strong validation. The tooltips have different designs and appearances. It seems like the app needs some QA attention to fix these bugs.
Yevhenii, QA engineer

Yevhenii, QA engineer

Need a reliable QA partner?

Hire us