Bugs Found in Read AI SaaS
Read AI is an innovative platform that seeks to redefine the boundaries of artificial intelligence and text analysis. It leverages AI aiming to extract meaningful data with higher accuracy and efficiency.
With an array of functionalities, the Read AI platform focuses on processing text from meetings, emails, and messages from any device. Moreover, it also uses advanced algorithms to constantly improve its analysis techniques and increase its efficiency.
Our team at QAwerk conducted an in-depth bug crawl on Read AI and discovered several bugs that could hinder performance and affect the user experience. We invite you, our readers, to explore these findings and learn how seemingly minor UI issues directly affect users.
AI chatbot incorrectly includes completed meetings in upcoming meetings list
Severity:
Major
Precondition:
- The user is logged in.
- The user has both completed and upcoming meetings for the same day on the calendar.
- The upcoming meetings should consist of one without a Google Meet link and another with it.
Steps to Reproduce:
- Log into the app.
- Navigate to the ‘Calendar’page.
- Verify that the ‘Upcoming’ section displays only future meetings.
- Open the AI chatbot.
- Enter the following prompt: ‘Get me a list of upcoming meetings’.
- Observe the chatbot’s response.
Environment:
OS: Windows 10
Chrome Version 150.0.7871.129
Firefox Version 151.0.3
Edge Version 150.0.4078.83
Actual Result:
The chatbot erroneously includes meetings from the current day that are already completed in its list of upcoming meetings, for example:
- Meet Meeting (01:44–01:49)
- Meet Meeting (01:57–01:57)
- Test (04:30–05:30)
- Test 2 (11:30–12:30).
Expected Result:
The chatbot should only list meetings that have not started or are unfinished. Completed meetings should be excluded from the list of upcoming meetings.
Header ‘Back’ button returns user to onboarding flow after onboarding completion
Severity:
Major
Precondition:
The user has completed account registration.
Steps to Reproduce:
- Register a new account.
- Complete the onboarding process.
- Allow the application to redirect to the main page.
- Click the ‘Back’ button in the application header.
Environment:
OS: Windows 10
Chrome Version 150.0.7871.129
Firefox Version 151.0.3
Edge Version 150.0.4078.83
Actual Result:
The user is redirected to the onboarding flow, despite having already completed it.
Expected Result:
Once the onboarding process is completed, clicking on the ‘Back’ button in the application header should not redirect the user back to the onboarding process.
Edit option is available for read-only folders and results in misleading error
Severity:
Major
Precondition:
- The user is logged in.
- The user has access to a folder with ‘Viewer (read-only)’ permissions.
Steps to Reproduce:
- Open a folder to which you only have read-only access.
- Click the ‘…’ (More actions) button.
- Select the ‘Edit’ option.
- Make any changes to the folder.
- Click the ‘Save’ button.
Environment:
OS: Windows 10
Chrome Version 150.0.7871.129
Firefox Version 151.0.3
Edge Version 150.0.4078.83
Actual Result:
Despite having read-only permissions, the ‘Edit’ option is available to the user. After clicking the ‘Save’ button, the operation fails, and the user is presented with a generic error message: ‘Failed to update folder. Please try again.’
Expected Result:
The ‘Edit’ option should be either disabled or hidden for users without edit permissions. Users who have read-only access should not be capable of modifying the folder settings.
Read-only sample reports can be selected when creating folders, resulting in misleading error
Severity:
Major
Precondition:
The user is logged in.
Steps to Reproduce:
- Navigate to the ‘Folders’ page.
- Create a new folder.
- In the ‘Add Reports’ dialog, observe that read-only sample reports are available for selection.
- Select one or more read-only reports.
- Click the ‘Save Changes’ button.
Environment:
OS: Windows 10
Chrome Version 150.0.7871.129
Firefox Version 151.0.3
Edge Version 150.0.4078.83
Actual Result:
The operation fails with the generic error message: ‘Failed to update folder reports. Please try again.’
Expected Result:
Reports that the user does not have permission to add should either not be displayed in the ‘Add Reports’ dialog or they should be clearly marked as unavailable and should not be selectable. Alternatively, the error message should explicitly state that the selected reports cannot be added due to insufficient user permissions.
‘Sample Reports - Read AI’ folder loads slowly on first access for new users
Severity:
Minor
Precondition:
The user has a newly registered account.
Steps to Reproduce:
- Register a new account.
- Navigate to the ‘Folders’ page.
- Open the ‘Sample Reports – Read AI’ folder.
- Observe the loading process.
- Refresh the webpage and reopen the same folder.
Environment:
OS: Windows 10
Chrome Version 150.0.7871.129
Firefox Version 151.0.3
Edge Version 150.0.4078.83
Actual Result:
During the first access, the ‘Sample Reports – Read AI’ folder takes an excessive amount of time to load, as indicated by a prolonged loading animation. After refreshing the page, the reports are loaded almost instantly.
Expected Result:
Sample reports should load in a timely manner during initial access, eliminating the need for a page refresh. The speed of loading should be consistent across the initial and subsequent visits.
During testing of Read.ai, I identified several UI bugs as well as an issue with the chatbot's understanding of what ‘upcoming meetings’ are. I recommend thorough usability and UI/UX testing to ensure the app lives up to its true potential.
