Bugs found in Pitch | Collaborate on Decks for Android
Pitch is a SaaS app designed to make creating, collaborating, and sharing presentations easier. The Pitch collaborative platform will help you turn your personal or team presentation into a professional brand tool for closing deals, winning clients, and expanding accounts.
The Pitch app provides valuable features, such as customizable templates, real-time editing, automated formatting, and seamless integration with several popular tools like Slack, Google Sheets, and Figma. This blend of features makes it an all-in-one workspace, providing users a smooth and efficient presentation-making experience.
Within our Bug Crawl project, the QAwerk team tested the Pitch app and highlighted some points for its improvement. We invite you to explore the results of our work.
Non-clickable functional buttons on opened presentation page
Severity:
Critical
Precondition:
- The user logged into the app.
- The user has created a workspace.
- Switch the presentation to the ‘Full Screen’ mode, block the screen.
Steps to Reproduce:
- Open the minimized presentation screen.
- Try to tap on the buttons on the screen.
Environment:
Android 12, Redmi Note 10 Pro
Actual Result:
It is not possible to tap on any buttons on the opened page.
Expected Result:
It should be possible to use all the buttons on the screen.
Keyboard does not close when presentation screen is opened in ‘Full Screen’ mode
Severity:
Major
Precondition:
- The user logged into the app.
- The user has created a workspace.
Steps to Reproduce:
- Open the app.
- Tap on the presentation in the ‘Recent’ block.
- Tap on the ‘Comment’ button.
- Tap on the ‘Full Screen’ button.
Environment:
Android 12, Redmi Note 10 Pro
Actual Result:
The keyboard does not close when the presentation screen is opened in the ‘Full Screen’ mode.
Expected Result:
The keyboard should be closed.
User profile name is not displayed in ‘Comments’ if name has special symbols
Severity:
Minor
Precondition:
- The user logged into the app.
- The user has created a workspace.
Steps to Reproduce:
- Open the app.
- Tap on the presentation in the ‘Recent’ block.
- Tap on the ‘Comment’ button.
- Enter a comment.
- Tap on the ‘Send’ button.
Environment:
Android 12, Redmi Note 10 Pro
Actual Result:
The user profile name is not displayed in the ‘Comments’ screen if the name has special symbols.
Expected Result:
The name should be displayed.
‘Reply to null’ is displayed after attempting to reply to comment
Severity:
Minor
Precondition:
- The user logged into the app.
- The user has created a workspace.
Steps to Reproduce:
- Open the app.
- Tap on the presentation in the ‘Recent’ block.
- Tap on the ‘Comment’ button.
- Enter a comment message.
- Tap on the ‘Send’ button.
- Tap on the ‘Reply’ button.
Environment:
Android 12, Redmi Note 10 Pro
Actual Result:
‘Reply to null’ is displayed after attempting to reply to the comment.
Expected Result:
‘Reply to {comment_text}’ should be displayed.
It is possible to send empty comment
Severity:
Minor
Precondition:
- The user logged into the app.
- The user has created a workspace.
Steps to Reproduce:
- Open the app.
- Tap on the presentation in the ‘Recent’ block.
- Tap on the ‘Comment’ button.
- Enter one symbol to the ‘Input’ field.
- Tap on the backspace and then on the ‘Send’ button.
Environment:
Android 12, Redmi Note 10 Pro
Actual Result:
An empty comment appears.
Expected Result:
The comment without symbols shouldn’t be displayed.
User profile name is not displayed in ‘Reaction’ screen if name has special symbols
Severity:
Minor
Precondition:
- The user logged into the app.
- The user has created a workspace.
Steps to Reproduce:
- Open the app.
- Tap on the presentation in the ‘Recent’ block.
- Tap on the ‘Reaction’ button.
- Select the reaction.
Environment:
Android 12, Redmi Note 10 Pro
Actual Result:
The user profile name is not displayed in the ‘Reaction’ screen if the name has special symbols.
Expected Result:
The name should be displayed.
I performed functional and UI/UX testing on the Pitch app for Android. The testing showed several substantial
bugs related to improper button functioning and keyboard behavior in the full-screen mode. I recommend
optimizing the interface in full-screen mode and ensuring an accurate display of user data, especially those
containing special characters.
