Bugs‌ ‌found‌ ‌in‌ Planable Social Media Approval for Android

Planable Social Media Approval

3.1

Planable is a collaboration tool designed to streamline social media planning and management. It serves as a central hub for teams to create, review, and schedule content across various social networks from a unified platform.

With features like team collaboration, post previews, and multi-level approval processes, Planable enhances how teams manage content production. Its intuitive interface allows for easy experimentation with different posting layouts and schedules, ensuring a smooth and visually appealing content management experience.

At QAwerk, we conducted an in-depth QA test of the Planable mobile app for Android. Our testing revealed a few bugs that might affect performance and user experience. We’re excited to share our findings and offer insights on how Planable can be further refined to better meet your social media planning needs.

10K+downloads
243 ratings

“User not found [403]” error on Password Recovery screen with invalid credentials

Severity:

Critical

Precondition:

A user on the Password Recovery screen.

Steps to Reproduce:
  1. Enter invalid email.
  2. Tap on the ‘Submit’ button.
Environment:

OS: Android 12
Device: Redmi Note 10 Pro

Actual Result:

“User not found [403]” error appears.

Expected Result:

The message should confirm a successful password recovery request.

Missing ‘+’ button in Workspace tab for Feed/Grid views

Severity:

Critical

Precondition:
  1. The user logged into the app.
  2. The user is on the Workspace tab.
Steps to Reproduce:
  1. Change view from Feed to Grid view.
  2. Pay attention to the screen.
Environment:

OS: Android 12
Device: Redmi Note 10 Pro

Actual Result:

The ‘+’ button is missing from the Feed and Grid view screens.

Expected Result:

The ‘+’ button should be visible on the Feed and Grid view screens, enabling the addition of new posts.

White screen with loader appears on Calendar view page after tapping “+ New Post” button

Severity:

Critical

Precondition:
  1. The user logged into the app.
  2. The user is on the Workspace tab.
Steps to Reproduce:
  1. Change view on Calendar.
  2. Tap on the “+ New Post” button.
Environment:

OS: Android 12
Device: Redmi Note 10 Pro

Actual Result:

White screen with loader appears.

Expected Result:

A new post creation page should be displayed.

User unable to create post in Media Library; white screen with loader appears

Severity:

Critical

Precondition:
  1. The user logged into the app.
  2. The user has uploaded a media file to the Media Library.
  3. The user is on the Media Library screen.
Steps to Reproduce:
  1. Tap on the ‘Select’ button.
  2. Select a file from the list.
  3. Tap on the ‘Create Post’ button.
Environment:

OS: Android 12
Device: Redmi Note 10 Pro

Actual Result:

The white screen with a loader appears on the Media Library screen after tapping the “Create Post” button.

Expected Result:

The user should be able to create a post without encountering a white screen.

Submit button is active on Password Recovery screen with empty input field

Severity:

Minor

Precondition:

A user is on the Password Recovery screen.

Steps to Reproduce:
  1. Pay attention to the ‘Submit’ button.
  2. Tap on the ‘Submit button’.
Environment:

OS: Android 12
Device: Redmi Note 10 Pro

Actual Result:

The ‘Submit’ button is active on the Password Recovery screen with an empty input field. The error ‘Something wrong’ appears after tapping the ‘Submit’ button.

Expected Result:

The ‘Submit’ button should be disabled when the input field is empty. It should not be possible to tap the ‘Submit’ button.

‘User not found [404]’ error appears on Log in screen after attempting to log in with incorrect credentials

Severity:

Minor

Precondition:

The user is on the Log In screen.

Steps to Reproduce:
  1. Enter an invalid email and password.
  2. Tap on the ‘Log in’ button.
Environment:

OS: Android 12
Device: Redmi Note 10 Pro

Actual Result:

‘User not found [404]’ error appears on the Log in screen after attempting to log in with incorrect credentials.

Expected Result:

‘Couldn’t find the user. Please sign up for an account on the web’ notification message appears.

During testing of the Planable app, I found some critical issues with adding and creating posts and managing accounts. Functional and user interface tests revealed several bugs that could impact user experience. I recommend integrating automated testing tools and conducting thorough regression tests to improve stability and prevent similar issues in future releases.
Yaroslav, QA engineer

Yaroslav, QA engineer

Need a reliable QA partner?

Hire us