Bugs‌ ‌found‌ ‌in‌ Referrizer SaaS

Referrizer

Referrizer SaaS is an exceptional tool for businesses looking to expand their customer base, increase customer engagement, and boost their online reputation.

The platform offers effective referral marketing strategies, engaging website pop-ups, and appealing landing pages, ensuring that businesses can reach a wide audience and enhance their reputation on popular platforms such as Google, Yelp, and Facebook. Referrizer provides a range of tools to help businesses build and protect their ratings on multiple review sites. With already more than 13,500 businesses experiencing growth, Referrizer has established itself as a trusted solution.

QAwerk’s software testers thoroughly tested Referrizer SaaS to make it even more attractive to users. Here is what can be improved right now.

Error is displayed on "Sign up" page for mismatched phone numbers

Severity:

Critical

Precondition:

The user is on the “Contact Info” step of the sign-up flow.

Steps to Reproduce:
  1. Please fill in all the required fields on the “Contact Info” page.
  2. Click the “Next” button.
  3. Fill in the “Mobile Phone Number” field using a phone number that is different from the value on the “Contact Info” page.
  4. Click the “Text Me Now” button.
  5. Enter the code sent to your phone.
  6. Click the “Finish” button.
Environment:

Google Chrome v.113.0.5672.127
Microsoft Edge v.113.0.1774.57
Firefox v.113.0.2

Actual Result:

The error message “Failed to save business. Please try again” is displayed.

Expected Result:

The app should handle the scenario when the mobile phone value is different. At least, a validation message with a clear description should be displayed.

Error is displayed on Sign up page for mismatched phone numbers

Optional label is displayed for mandatory field on "Use Contact" form

Severity:

Major

Precondition:

The user is on the “Contact us” page.

Steps to Reproduce:
  1. Fill in all the fields except for the Subject field.
  2. Click the “Send” button.
Environment:

Google Chrome v.113.0.5672.127
Microsoft Edge v.113.0.1774.57
Firefox v.113.0.2

Actual Result:

The validation message “This is a required field” is being displayed under the Subject field.

Expected Result:

The “Optional” label should not be displayed for the mandatory fields.

Optional label is displayed for mandatory field on Use Contact form

Validation message "Must be less than 100 characters" is displayed under “Subject” field

Severity:

Major

Precondition:

The user is on the “Contact us” page.

Steps to Reproduce:

Enter 32 characters into the “Subject” field.

Environment:

Google Chrome v.113.0.5672.127
Microsoft Edge v.113.0.1774.57
Firefox v.113.0.2

Actual Result:

If the value entered in the “Subject” field consists of fewer than 100 characters, the validation message “Must be less than 100 characters” is displayed.

Expected Result:

The validation message should be displayed if the user attempts to exceed the maximum character limit.

Validation message Must be less than 100 characters is displayed under “Subject” field

It’s possible to deduct credit/loyalty points with zero balance

Severity:

Major

Precondition:
  1. The user is logged in.
  2. A contact with zero balance of both credit and loyalty points is opened.
Steps to Reproduce:
  1. Scroll down to the “Manual Adjustments” section on the contact record.
  2. Click the minus button next to “Reward Credit.”
  3. Verify that the “Deduct Credit” modal window is displayed.
  4. Ensure that the default value is set to 1.
  5. Click the “Deduct” button.
Environment:

Google Chrome v.113.0.5672.127
Microsoft Edge v.113.0.1774.57
Firefox v.113.0.2

Actual Result:

After entering any value greater than 0, the validation message “Max number 0” is displayed. If the user enters 0 into the input field, the validation message “The number must be greater than zero” is displayed. The same behavior applies to “Loyalty” points.

Expected Result:

The app should handle the scenario where the user has a zero balance of credit/loyalty points. The minus button should be inactive, or the app should display the appropriate validation messages.

Impossible to share case study to Telegram and Pinterest

Severity:

Major

Precondition:

The user is on the “Case Studies” page.

Steps to Reproduce:
  1. Select an article from the list.
  2. Click the “Share” button.
  3. Choose Telegram or Pinterest from the list of available messengers and social networks.
Environment:

Google Chrome v.113.0.5672.127
Microsoft Edge v.113.0.1774.57
Firefox v.113.0.2

Actual Result:

Nothing happens after clicking the Telegram and Pinterest icon.

Expected Result:

The user should be able to share the case study on all the listed messengers and social networks.

It’s possible to add tag with empty value to “Contact” record

Severity:

Minor

Precondition:
  1. The user is logged in to the app.
  2. At least one contact has been created.
Steps to Reproduce:
  1. Open an existing contact record.
  2. Click the plus button in the “Tags” section.
  3. Select the “Create new tag” option.
  4. Enter a space in the Name input field.
  5. Click the “Create” button.
Environment:

Google Chrome v.113.0.5672.127
Microsoft Edge v.113.0.1774.57
Firefox v.113.0.2

Actual Result:

The tag with an empty record has been successfully created.

Expected Result:

The app should perform validation on empty values.

It’s possible to add tag with empty value to “Contact” record

No validation on “Birth Date” field if user enters future date

Severity:

Minor

Precondition:
  1. The user is logged in to the app.
  2. There is at least one existing contact record.
Steps to Reproduce:
  1. Navigate to any existing contact record.
  2. Select the “Edit” option.
  3. Enter a future date in the “Birth Date” field.
  4. Click the “Save” button.
Environment:

Google Chrome v.113.0.5672.127
Microsoft Edge v.113.0.1774.57
Firefox v.113.0.2

Actual Result:

No validation messages are displayed, and the random date is saved successfully.

Expected Result:

The app should display validation messages when the user enters invalid values.

During testing, I encountered numerous issues related to validation. I strongly recommend placing more emphasis on negative scenarios and ensuring that the validation messages are clear for end users.
Tetiana, QA engineer

Tetiana, QA engineer

Need a reliable QA partner?

Hire us