Bugs Found in Laxis
Laxis is a versatile AI-powered platform designed to streamline and optimize your note-taking during meetings. It provides a convenient solution for recording and summarizing information and includes an AI Chat feature to help retrieve facts fast.
The AI Dictation feature lets users stop typing reminders and use the Laxis voice keyboard to capture insights and ideas as they come. The app integrates this feature with popular messaging clients, browsers, and apps.
Our team at QAwerk conducted a detailed Bug Crawl of Laxis and discovered several bugs. Most of them are in the solution’s UI. Take a look at the detailed report below.
Unable to create new folder immediately after creating folder
Severity:
Major
Steps to Reproduce:
- Click the ‘+’ button next to the folder button in the sidebar.
- Enter a valid folder name.
- Click the ‘Create Folder’ button.
- Click the ‘+’ button next to the folder button in the sidebar again while the ‘Folder created’ toast notification is displayed.
- Observe the folder creation modal.
- Enter or modify the folder name and other required fields.
Environment:
Operating System: Windows 10
Chrome version 150.0.7871.129
Firefox version 151.0.3
Actual Result:
The folder creation modal opens with the previously entered folder name. The ‘Create Folder’ button remains disabled despite changes to the required fields. A new folder can only be created after reloading the page.
Expected Result:
The folder creation modal should open with reset fields, and the ‘Create Folder’ button should become active when all required fields contain valid values, allowing the user to create another folder immediately.
‘Description’ field input limit does not match allowed character limit
Severity:
Major
Steps to Reproduce:
- Open the ‘AI Template’ creation form.
- Enter a large Lorem Ipsum text into the ‘Description’ field.
- Observe that the text input is limited to ‘1024 characters’.
- Save the AI Template after entering the maximum allowed text.
Environment:
Operating System: Windows 10
Chrome version 150.0.7871.129
Firefox version 151.0.3
Microsoft Edge v150.0.4078.83
Actual Result:
The ‘Description’ field allows up to ‘1024 characters’, but only ‘500 characters’ are actually allowed when saving the AI Template. An error is displayed indicating that the description can contain a maximum of 500 characters.
Expected Result:
The input field limit and the backend validation limit should be consistent. The ‘Description’ field should allow exactly the same number of characters as specified by the actual validation limit.
Empty meeting transcription remains stuck in processing indefinitely
Severity:
Major
Precondition:
The user must be logged in.
Steps to Reproduce:
- Click the ‘New Recording’ button.
- Start the recording.
- Do not say anything for 10–20 seconds.
- Click the ‘Stop’ button to finish the recording.
- Click the ‘Back’ button.
- Observe the newly created meeting.
Environment:
Operating System: Windows 10
Chrome version 150.0.7871.129
Firefox version 151.0.3
Microsoft Edge v150.0.4078.83
Actual Result:
The newly created meeting remains in the ‘Processing’ status. The meeting cannot be opened while it is being processed. The processing status remains unchanged even after several days.
Expected Result:
Empty recordings should be processed successfully or marked with an appropriate status indicating that no transcription could be generated. A meeting recording should not remain in the ‘Processing’ state indefinitely. If processing fails, the user should receive a clear error or failure message.
‘Pause’ button does not stop active meeting recording
Severity:
Major
Precondition:
The user must be logged in.
Steps to Reproduce:
- Click the ‘New Recording’ button.
- Start a meeting recording.
- While the recording is in progress, click the ‘Pause’ button.
- Observe the recording status.
Environment:
Operating System: Windows 10
Chrome version 150.0.7871.129
Firefox version 151.0.3
Microsoft Edge v150.0.4078.83
Actual Result:
The recording continues after clicking the ‘Pause’ button.
Expected Result:
Clicking the ‘Pause’ button should pause the active recording.
Selecting active meeting in meetings list does not open meeting
Severity:
Major
Precondition:
The user must be logged in.
Steps to Reproduce:
- Click the ‘New Recording’ button.
- Start the meeting recording.
- Wait for 10–20 seconds.
- Click the ‘Back’ button without stopping the recording.
- In the meetings list, click the active meeting.
- Observe the result.
Environment:
Operating System: Windows 10
Chrome version 150.0.7871.129
Firefox version 151.0.3
Microsoft Edge v150.0.4078.83
Actual Result:
The active meeting does not open. An error message indicates that the meeting is still being processed. Clicking the ‘New Recording’ button returns the user to the active meeting.
Expected Result:
Clicking an active meeting in the meetings list should open it.
Workspace name field displays long technical error log for excessively long input
Severity:
Major
Precondition:
The user must be logged in.
Steps to Reproduce:
- Navigate to the ‘Settings’ section.
- Open the ‘Workspace’ tab.
- Enter a very long text (e.g., Lorem Ipsum) into the ‘Name’ field.
- Click the ‘Checkmark’ button next to the field.
- Observe the notification.
Environment:
Operating System: Windows 10
Chrome version 150.0.7871.129
Firefox version 151.0.3
Microsoft Edge v150.0.4078.83
Actual Result:
A toast notification containing a long technical error log is displayed.
Expected Result:
The ‘Workspace 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 character limit has been exceeded. Technical error logs should not be displayed to the user.
Profile fields display generic save error when excessively long values are entered
Severity:
Minor
Precondition:
The user must be logged in.
Steps to Reproduce:
- Navigate to the ‘Settings’ section.
- Open the ‘Profile’ tab.
- Enter a very long text (e.g., Lorem Ipsum) into a profile field.
- Repeat the same action for other available profile fields.
- Observe the displayed notifications.
Environment:
Operating System: Windows 10
Chrome version 150.0.7871.129
Firefox version 151.0.3
Microsoft Edge v150.0.4078.83
Actual Result:
A generic toast error ‘Profile save failed, please try again’ is displayed for each field with an excessively long value.
Expected Result:
Profile fields should have a clearly defined maximum character limit. The user should either be prevented from entering more characters than allowed or receive a clear validation error indicating that the maximum character limit has been exceeded.
Folder creation modal stretches across the entire screen
Severity:
Minor
Steps to Reproduce:
- Click the ‘+’ button next to the ‘Folder’ button in the sidebar.
- Observe the folder creation modal.
Environment:
Operating System: Windows 10
Chrome version 150.0.7871.129
Firefox version 151.0.3
Microsoft Edge v150.0.4078.83
Actual Result:
The folder creation modal stretches across the entire screen. The modal content is positioned on the left side and occupies only a small portion of the screen, while the modal background covers the entire screen width.
Expected Result:
The folder creation modal should have an appropriate fixed or content-based width, with the modal content properly centered on the screen.
Generic error message is displayed when creating folder with invalid name
Severity:
Minor
Precondition:
The user must be logged in.
Steps to Reproduce:
- Click the ‘+’ button next to the ‘Folder’ button in the sidebar.
- Enter a folder name containing one character and try to create the folder.
- Repeat the steps with a folder name containing 2 characters.
- Repeat the steps with a very long folder name.
Environment:
Operating System: Windows 10
Chrome version 150.0.7871.129
Firefox version 151.0.3
Microsoft Edge v150.0.4078.83
Actual Result:
The same generic error message ‘Folder creation failed’ is displayed in all three cases, without indicating why the folder name is invalid.
Expected Result:
A specific and informative validation error message should be displayed, indicating whether the folder name is too short or too long.
While testing Laxis, I identified multiple UI errors, although the app’s core functionality performed without any critical issues. I recommend thorough UI/UX testing to ensure the app delivers the best possible experience for users.
