Mimo for Android/iOS. Weekly Bug Crawl by QAwerk

Mimo for Android/iOS

Mimo may become the thing that would drag you into the programming. Even if you have a tight schedule, “byte-sized” lessons in this app will give you the knowledge you need without dragging you from any important matters. An app contains lessons regarding all of the most popular programming languages. You will be able to learn how to make your own apps, games, websites, and may even hack something in the process. But even in an application so IT-oriented, our Bug Crawl has still managed to find some serious flaws. And here they are.

0 ratings

App lets you Sign Up with the same email address several times allowing access to the primary account when registering with a secondary way

Severity:

Critical

Steps to Reproduce:
  1. Register via Google+ account on an Android device.
  2. Register once again but via email address that is used in the same Google+ account(this will be a duplicate).
  3. Log in to a duplicate account on another device. We used an iPhone 6.
  4. Notice how there are no added courses yet. GIF1
  5. Add any courses in a G+ account on a primary device. GIF2
  6. Check added courses in the duplicate account on another device. GIF3
Environment:

Xiaomi Mi Mix 2 (Android 8.0.0),
iPhone 6 (iOS 11.3.1)

Actual Result:

Duplicate account can be created if you know an email address of a user. And all the changes in one account are also made in another.

Expected Result:

Duplicate account creation should not be allowed.

Disappearing ‘Try Again’ pop-up message

Severity:

Minor

Steps to Reproduce:
  1. Choose the incorrect answer.
  2. Ignore the proposal to try again and choose another answer.
Environment:

Xiaomi Mi Mix 2 (Android 8.0.0)

Actual Result:

‘Try Again’ pop-up message disappears when you choose the right answer.

Expected Result:

When a “Try Again” pop-up message is shown, there should be no way to continue the test.

The app’s gotten our attention with the first bug specifically. You would think “How scary! Someone’s going to complete my tests for me”, but if a bug of that kind would hide in an app with an access to your bank account, it would end badly. A given app is of a great use for a lot of people, but today it’s going to be an example of how not to make a registration form in your application.
Eugene, QA engineer

Eugene, QA engineer

Need a reliable QA partner?

Hire us