Bugs‌ ‌found‌ ‌in‌ Popwork SaaS

Popwork

Popwork is an intuitive workspace that streamlines the performance of managers and their teams.

It is suitable for CEOs and HRs, senior and junior managers, as well as remote managers. With Popwork, companies can easily prepare weekly one-on-one meetings with their employees. Designed by and for teams, Popwork helps every team reach its full potential at work. The platform offers a free 21-day trial to show its users how it can transform their management practices and boost team engagement.

Our QA engineers decided to manually test the performance of Popwork SaaS. Here are some of the most prominent Popwork bugs we found.

400 Error occurs after creating new team via “Resume onboarding”

Severity:

Major

Precondition:
  1. The user is signed up.
  2. The user completed the onboarding flow (with creating a team and inviting at least 1 member to the team).
Steps to Reproduce:
  1. Hover over the name of the recently created team on the left navbar.
  2. Click the 3-dots button.
  3. Click the “Change manager” button.
  4. Select the invited member from the dropdown and click the “Confirm change” button.
  5. Click the “Resume onboarding” button on the bottom.
  6. Enter a new team name and click the “Continue” button.
Environment:

Windows 10 Pro
Chrome 109.0.5414.76, Firefox 109.0.1, Edge 110.0.1587.41

Actual Result:

The user is redirected back to the “Dashboard” page; the team is not created; 400 Error occurs in the browser console.

Expected Result:

The second step of onboarding “Name your team” is marked as completed; the form of the third step “Review the questions for your team” is expanded.

It’s possible to save question with empty content

Severity:

Minor

Precondition:
  1. The user is signed up.
  2. The user completed the onboarding flow (with creating a team and inviting at least 1 member to the team).
Steps to Reproduce:
  1. Click the “Management rituals” navbar item.
  2. Click the “Questions” button below the team title.
  3. Hover over any list items (except for the 1st and 2nd ones).
  4. Click the “Edit” button.
  5. Clear the “QUESTION” input field.
  6. Switch the language next to the title of the “QUESTION” input field.
  7. Clear the “QUESTION” input field.
  8. Click the “Save changes” button.
Environment:

Windows 10 Pro
Chrome 109.0.5414.76, Firefox 109.0.1, Edge 110.0.1587.41

Actual Result:

A question with missing content is saved.

Expected Result:

A question with missing content should not be saved; the “QUESTION” input field is required.

“Edit rituals” menu item opens wrong form

Severity:

Minor

Precondition:
  1. The user is signed up.
  2. The user completed the onboarding flow (with creating a team and inviting at least 1 member to the team).
Steps to Reproduce:
  1. Click the “Management rituals” navbar item.
  2. Click the 3-dots button on the right from the title of the team.
  3. Click the “Edit rituals” menu item.
Environment:

Windows 10 Pro
Chrome 109.0.5414.76, Firefox 109.0.1, Edge 110.0.1587.41

Actual Result:

The form for editing the team opens.

Expected Result:

The form for editing the rituals should open.

Form closes with success message instead of error message

Severity:

Minor

Precondition:
  1. The user is signed up.
  2. The user completed the onboarding flow (with creating a team and inviting at least 1 member to the team).
Steps to Reproduce:
  1. Click the “Objectives” navbar item.
  2. Click the “+ Create objective” button.
  3. Fill in the “Objective” input field.
  4. Select a date from the “Due date” calendar field.
  5. Click the “Add objective” button (leave the “Owner” selector field empty).
Environment:

Windows 10 Pro
Chrome 109.0.5414.76, Firefox 109.0.1, Edge 110.0.1587.41

Actual Result:

The “Add objective” form closes; success message “Objective added” pops up (although the object was not created).

Expected Result:

The “Add objective” form should not close; the “Owner” selector field should be marked red.

“Edit objective” menu item is not relevant for closed objectives

Severity:

Trivial (Enhancement)

Precondition:
  1. The user is signed up.
  2. The user completed the onboarding flow (with creating a team and inviting at least 1 member to the team).
Steps to Reproduce:
  1. Click the “Objectives” navbar item.
  2. Click the “+ Create objective” button.
  3. Fill in the “Objective” input field.
  4. Select a member from Precondition 2 from the “Owner” selector field.
  5. Select a date from the “Due date” calendar field.
  6. Click the “Add objective” button.
  7. Click the record of the recently created objective.
  8. Click the 3-dots button in the pop-up on the right side.
  9. Click the “Close objective” menu item.
  10. Select any status from the selector field.
  11. Fill in the “Comment” input field.
  12. Click the “Close objective” button.
  13. Click the 3-dots button in the pop-up on the right side.
Environment:

Windows 10 Pro
Chrome 109.0.5414.76, Firefox 109.0.1, Edge 110.0.1587.41

Actual Result:

The “Edit objective” menu item is present, although a closed objective cannot be edited.

Expected Result:

The “Edit objective” menu item should not be present for closed objectives.

During testing, several bugs were found: a 400 bad request error, possibility to save a question with no content, inappropriate success message, “Edit rituals” menu item opening a wrong form, and the presence of irrelevant items. In all other respects, the app works properly.
Aliaksei, QA engineer

Aliaksei, QA engineer

Need a reliable QA partner?

Hire us