Bugs Found in Supernormal SaaS
Supernormal is a platform designed to streamline your work processes. It offers efficient functionalities such as task tracking, real-time collaboration, and note-taking. The product is AI-powered and offers a wide range of integrations to make it more convenient to use in today’s digital business environment.
When the QAwerk team conducted a thorough bug crawl of Supernormal, we discovered bugs that impact user experience, as most of them are UI-related. We invite you to see our detailed report if you want to understand how this technically efficient app breaks user trust.
AI agent takes several minutes to process tasks containing Base64-encoded input
Severity:
Major
Precondition:
- The user is logged in.
- The AI Agent is available.
Steps to Reproduce:
- Click the ‘New Task’ option.
- Enter a prompt containing a Base64-encoded string that needs to be decoded.
- Submit the task.
- Observe the AI agent’s response time.
- Repeat the same task without the Base64 decoding requirement.
Environment:
OS: Windows 10
Chrome 150.0.7871.129
Firefox 151.0.3
Edge 150.0.4078.83
Actual Result:
The AI agent becomes unresponsive after submitting a task containing Base64 input. The response is generated only after approximately 5 minutes. The same task without Base64 decoding is processed immediately.
Expected Result:
Tasks containing Base64-encoded input should be processed within a reasonable response time. The AI agent should not become unresponsive or require several minutes to process the request.
Invalid file size error is displayed only after sending message with attachment
Severity:
Major
Precondition:
- The user is logged in.
- The user has access to the ‘New Task’ chat.
Steps to Reproduce:
- Navigate to the ‘New Task’ page.
- Click the ‘+’ button in the chat.
- Upload an image larger than 10 MB.
- Enter a question related to the uploaded image.
- Click the ‘Send’ button.
Environment:
OS: Windows 10
Chrome 150.0.7871.129
Firefox 151.0.3
Edge 150.0.4078.83
Actual Result:
The file size error is displayed only after the message is sent. The question is still processed by the AI agent even though the image was not successfully uploaded. As a result, the agent provides an incorrect response because it does not have access to the image. This may also unnecessarily consume user credits.
Expected Result:
The file size validation error should be displayed immediately when the user attempts to upload an unsupported file. Alternatively, sending the message should be blocked if the attachment is invalid. The user should be clearly informed that the file cannot be uploaded before the request is sent to the AI agent.
Profile name field has no character limit validation and returns generic server error
Severity:
Major
Precondition:
The user is logged in.
Steps to Reproduce:
- Navigate to the ‘Settings’ section.
- Open the ‘Profile’ tab.
- Enter a very long text (e.g., Lorem Ipsum) into the ‘Name’ field.
- Click the ‘Save’ button.
Environment:
OS: Windows 10
Chrome 150.0.7871.129
Firefox 151.0.3
Edge 150.0.4078.83
Actual Result:
The application attempts to process the request for an extended period of time. The request eventually fails with a generic ‘We’ll be right back’ error message displayed. No validation message indicates that the entered name exceeds the allowed length.
Expected Result:
The ‘Name’ field should have a defined maximum character limit. The user should either be prevented from entering more characters than allowed or receive a clear validation message indicating that the maximum length has been exceeded. The request should not trigger a generic server error message.
Billing page displays incorrect information about ‘Free’ plan monthly credits
Severity:
Major
Precondition:
A new user account is registered.
Steps to Reproduce:
- Register a new account.
- Navigate to the ‘Billing’ page.
- Review the ‘Free’ plan description.
- Check the number of credits assigned to the account after registration.
- Wait until the next monthly billing cycle and observe the credit balance.
Environment:
OS: Windows 10
Chrome 150.0.7871.129
Firefox 151.0.3
Edge 150.0.4078.83
Actual Result:
The ‘Billing’ page states that the Free plan includes ‘20 credits per month’. Newly registered users receive only ‘5 credits’. At the beginning of the next month, the credits are reset instead of being replenished to the advertised amount.
Expected Result:
The ‘Billing’ page should accurately describe how many credits ‘Free’ plan users receive and how the monthly credit renewal works. The information presented to users should be transparent and consistent with the actual billing behavior.
Deleting project from sidebar does not close project page
Severity:
Major
Precondition:
The user is logged in.
Steps to Reproduce:
- Create a new project.
- Click the project name in the left sidebar to open the project.
- Click the ‘…’ (More actions) button next to the project name in the sidebar.
- Click ‘Delete project’ option.
- Observe the current page after the project is deleted.
Environment:
OS: Windows 10
Chrome 150.0.7871.129
Firefox 151.0.3
Edge 150.0.4078.83
Actual Result:
The project is deleted, but the user remains on the deleted project’s page. The project page remains open even though the project no longer exists.
Expected Result:
After deleting the project from the sidebar, the project page should be closed automatically. The behavior should be consistent with the ‘Delete project’ action available in the project header.
Organization name field has no character limit validation
Severity:
Minor
Precondition:
The user is logged in.
Steps to Reproduce:
- Navigate to the ‘Settings’ section.
- Open the ‘General’ tab.
- Enter a very long text (e.g., Lorem Ipsum) into the ‘Organization Name’ field.
- Click the ‘Save’ button.
Environment:
OS: Windows 10
Chrome 150.0.7871.129
Firefox 151.0.3
Edge 150.0.4078.83
Actual Result:
The application immediately displays a generic error message: ‘Failed to save organization name.’ The error does not indicate that the entered value exceeds the allowed character limit.
Expected Result:
The ‘Organization Name’ field should have a defined maximum character limit. The user should either be prevented from entering more characters than allowed or receive a clear validation message indicating that the maximum length has been exceeded. A generic save error should not be displayed for invalid input.
Project creation error does not provide information about invalid project name
Severity:
Minor
Precondition:
The user is logged in.
Steps to Reproduce:
- Click the ‘New project’ option and enter a one-character name.
- Try to create the project.
- Observe the error message.
- Create another project with an excessively long name.
- Try to create the project.
- Observe the error message.
Environment:
OS: Windows 10
Chrome 150.0.7871.129
Firefox 151.0.3
Edge 150.0.4078.83
Actual Result:
Project creation fails for both short and excessively long project names. The same generic project creation error is displayed in both cases. The error does not explain what is wrong with the entered project name.
Expected Result:
The application should validate the project name and provide a clear error message explaining the applicable requirements. For example, the message should indicate if the name is too short, too long, or otherwise invalid.
While testing this SaaS, I identified several issues with incomplete billing information for Free accounts and UI errors. I strongly recommend running a complete UI check to catch every bug and ensure that the user can get clear information from the app and trust it completely.
