Weight Loss Tracker, BMI for iOS. Weekly Bug Crawl by QAwerk

Weight Loss Tracker, BMI for iOS. Weekly Bug Crawl by QAwerk

Weight Loss Tracker, BMI for iOS

4.3

Body Weight Index is a thing that will let you know the weight that is best for you. And this app, Weight Loss Tracker, BMI will help you get yourself to that precious number. When you have a logging system, it’s much easier to see and maintain the improvements in your body. But let’s see if there’s anything to improve in this app…

82 ratings
Crash after you open an ‘All’ tab on a ‘Weight’ page if the future date is set
Severity:
Major

Steps to reproduce:
  1. Open the ‘Weight’ page.
  2. Tap on ‘+’.
  3. Select the future year in a date item (e.g. 2023).
  4. Tap on ‘Done’.
  5. Tap on ‘Save’.
  6. Select ‘All’ as a time period of the graph.

Environment:

iPhone 6s (iOS 11.4)

Actual result:

App crashes.

Expected result:

Future date can not be set.

Nothing happens when you tap some items, and the internet connection is OFF
Severity:
Minor

Pre-condition:

The internet connection is OFF.

Steps to reproduce:
  1. Open the ‘Settings’ page.
  2. Tap on ‘Remove advertisements’ or ‘Restore purchase’ or ‘Rate aktiBMI’.

Environment:

iPhone 6s (iOS 11.4)

Actual result:

Nothing happens.

Expected result:

Internet connection error message is shown.

Underweight item is not shown in the graph
Severity:
Minor

Steps to reproduce:
  1. Set ’50 kg’ in ‘Weight’.
  2. Set ’70kg’ in ‘Desired Weight’.
  3. Tap on ‘Save and continue’.
  4. Open ‘Weight’ page.

Environment:

iPhone 6s (iOS 11.4)

Actual result:

Underweight bar is hidden.

Expected result:

Underweight bar is shown in the graph.

The list of .db files is duplicated when you attempt to delete one of them
Severity:
Major

Pre-condition:

Several .db files are in the Import list.

Steps to reproduce:
  1. Open the ‘Settings’ page.
  2. Tap on ‘Import’.
  3. Tap on ‘Edit’.
  4. Delete any item in the list.

Environment:

iPhone 6s (iOS 11.4)

Actual result:

Items in the list are duplicated.

Expected result:

.db file is deleted successfully.

Crash during the attempt to import a .db file less than one minute after you reset entries
Severity:
Major

Steps to reproduce:
  1. Open the ‘Settings’ page.
  2. Tap on ‘Reset entries’.
  3. Set the data you need in less than 60 seconds.
  4. Tap on ‘Save and continue.
  5. Go to the ‘Settings’ page.
  6. Tap on ‘Import’ and choose the freshest .db file.

Environment:

iPhone 6s (iOS 11.4)

Actual result:

App crashes.

Expected result:

Import is successful.

Desired weight is shown only after you open an ‘All’ graph
Severity:
Major

Steps to reproduce:
  1. Open the ‘Weight’ page.
  2. Pay attention to the graph and try to find the ‘Desired weight’ line.
  3. Switch between graph tabs and come back to ‘Month’ graph tab.

Environment:

iPhone 6s (iOS 11.4)

Actual result:

Desired weight line is shown after you open ‘All’ tab.

Expected result:

Desired weight line is shown on every graph.

Inaccurate UI
Severity:
Minor

Steps to reproduce:
  1. Notice how the default data is 175cm, 80kg, Overweight.
  2. Tap on ‘+’.
  3. Set ‘79kg’ and save.
  4. Go to the ‘BMI’ page and pay attention to which color zone the arrow is in.

Environment:

iPhone 6s (iOS 11.4)

Actual result:

Arrow shows the beginning of the ‘Overweight’ zone.

Expected result:

Arrow shows the end of the ‘Normalweight’ zone.

Having your application checked for bugs even once goes a long way. Your customers become your long-term users when you free them from the frustration that can be caused by sudden crashes or empty, idle buttons and links. It’s a win-win for both of you. But even if you don’t have in-house QA engineers in your team, offshore QA is always an option. To have an additional point in expenses would seem to be excessive, but only until you try to assemble your own testing unit. Really, do try it out! And then compare the resulting cost to the software QA quotes on our website.

Some developers put all their efforts into making their software as flawless as possible and yet they still fail. To say that such developers are bad is surely rude and incorrect. The problem is that in-house teams that have already spent months developing an app know exactly what should work but have little to no idea about what is about to break.
Evgeniia, QA

Evgeniia, QA

Need a reliable QA partner?

Hire us