Bugs Found in MeetGeek AI SaaS
MeetGeek is a dynamic AI-powered platform designed to streamline the process of orchestrating meetings. The application aims to simplify scheduling and managing conference calls, making them more efficient and effective.
Diving deeper into its functionality, MeetGeek employs AI technology to set up meetings, provide agendas, send reminders, and even document key points. It works seamlessly with calendars and other organizational tools, making it a handy aid for individuals, teams, and businesses.
Our team at QAwerk conducted a robust bug crawl of MeetGeek, during which we identified several bugs that affect performance and user experience. We invite you to explore our findings and see how to make this powerful AI tool even better.
Meeting recorded by bot remains in processing state and is never completed
Severity:
Critical
Precondition:
- The user is logged in.
- The meeting recording bot is available.
- A Google Meet meeting is scheduled.
Steps to Reproduce:
- Schedule a meeting in Google Calendar.
- Start a Google Meet session.
- Start the transcription using the MeetGeek browser extension.
- Invite the recording bot to the meeting.
- Verify that both the extension and the bot are recording simultaneously.
- Stop both recordings and end the meeting.
- Open the application and monitor the processing status of both recordings.
Environment:
OS: Windows 10
Browsers tested: Chrome 148.0.7778.217, Firefox 151.0.3, Edge 148.0.3967.96
Actual Result:
The recording produced by the MeetGeek extension is successfully processed within a short period. The recording generated by the bot retains processing state and fails to complete even after waiting for 16 hours.
Expected Result:
Recordings made by the bot should be successfully processed within a reasonable timeframe, similar to other recording methods. After processing, the recording should be available along with the transcript, summary, and related meeting data.
‘Enable Brand Emails’ toggle can be changed on Free plan despite being marked as paid feature
Severity:
Major
Precondition:
The user is logged in with a Free plan account.
Steps to Reproduce:
- Navigate to the ‘Settings’ section.
- Scroll down to the ‘Enable Brand Emails’ option.
- Note the message informing the user that this feature is only available on the Business/Paid plans.
- Switch on the ‘Enable Brand Emails’ toggle.
Environment:
OS: Windows 10
Browsers tested: Chrome 148.0.7778.217, Firefox 151.0.3, Edge 148.0.3967.96
Actual Result:
The user can operate the toggle. When changing the setting, a toast notification that says ‘Preference updated’ appears. The user interface suggests that the change has been successfully applied, even though this feature is supposed to be available only for paid plan users.
Expected Result:
The ‘Enable Brand Emails’ switch should not be interactable by Free plan users. Alternatively, the feature should be made available without showing a message about the restriction to paid plans. The UI should not show a confirmation of activating a feature that is supposed to be restricted.
‘New’ badge is improperly displayed within ‘Voice Agents’ button on Firefox and Edge browsers
Severity:
Minor
Precondition:
The user is logged in.
Steps to Reproduce:
- Navigate to the ‘Downloads’ page.
- Locate the ‘Voice Agents’ button in the sidebar.
- ‘Observe the ‘New’ badge’s appearance.
- Conduct the same test on Chrome, Firefox, and Edge.
Environment:
OS: Windows 10
Browsers tested: Chrome 148.0.7778.217, Firefox 151.0.3, Edge 148.0.3967.96
Display: Full HD (1920×1080), Browser window maximized
Actual Result:
The ‘New’ badge appears partially clipped within the ‘Voice Agents’ button.
This ‘New’ badge does not appear in Firefox or Edge at all.
Expected Result:
The ‘New’ badge should fit completely within the ‘Voice Agents’ button without getting clipped. The badge should be visible consistently across all supported browsers.
‘Meeting Timeline’ displays invalid timestamp format as ‘00:60’
Severity:
Minor
Precondition:
- The user is logged in.
- An accessible meeting with a timeline exists.
Steps to Reproduce:
- Access the recording of a meeting.
- Navigate to the particular meeting’s timeline.
- Observe the timestamps exhibited on the timeline.
Environment:
OS: Windows 10
Browsers tested: Chrome 148.0.7778.217, Firefox 151.0.3, Edge 148.0.3967.96
Actual Result:
An incorrect timestamp format ‘00:60’ is displayed.
Expected Result:
The time values should adhere to a credible format. When the seconds counter reaches 60, the timestamp should progress to the next minute. Therefore, the timestamp must be shown as ‘01:00’ rather than the incorrect ‘00:60’.
‘New’ badge visibility in sidebar is inconsistent across pages
Severity:
Minor
Precondition:
The user is logged in.
Steps to Reproduce:
- Navigate to the ‘Past Meetings’ page.
- Observe the ‘New’ badge next to the ‘Voice Agents’ in the sidebar.
- Navigate to the ‘AI Chat’ page.
- Inspect the sidebar once more.
- Return to the ‘Past Meetings’ page.
Environment:
OS: Windows 10
Browsers tested: Chrome 148.0.7778.217, Firefox 151.0.3, Edge 148.0.3967.96
Actual Result:
The ‘New’ badge next to the ‘Voice Agents’ is visible on the ‘Past Meetings’ page but disappears on the ‘AI Chat’ page. Upon returning to the ‘Past Meetings’ page, the badge reappears.
Expected Result:
The visibility of sidebar badges should not change based on the currently selected page. The ‘New’ badge should maintain its visibility status, irrespective of page navigation.
During testing, I did not find any defects in the chatbot's performance and core features. However, I identified several critical issues within the SaaS platform itself, as well as a few minor bugs. I recommend a comprehensive QA check and regression testing to catch and resolve any bugs that currently hinder the platform.
