Not specified
11 proposals
Testing of a mobile application — calorie tracker
We are looking for a meticulous QA tester for comprehensive testing of a mobile application for calorie counting and dietary control.
The application is available on iOS and Android. The main feature is the recognition of dishes from a photo with automatic identification of ingredients, calorie content, and macronutrients.
Main tasks
Conduct complete functional testing of the application.
Check all available screens, buttons, scenarios, and possible user interactions with the application.
Identify functional, visual, logical, and UX errors.
Test the application over several days, simulating real user behavior.
Scan at least 50 different dishes or products and check the quality of recognition.
Verify the correctness of saving, editing, and deleting entered data.
Check the stability of the application after closing, restarting, and rebooting the device.
What needs to be checked
Registration and onboarding
Registration of a new user.
Login to an existing account.
Logout and re-login.
All response options during onboarding.
Correctness of the calculation of the recommended calorie and macronutrient intake.
Input of minimum, maximum, incorrect, and non-standard values.
Returning to previous screens and changing responses.
Application behavior after interrupting onboarding.
Food scanning
It is necessary to test at least 50 different dishes and products, including:
simple products;
complex multi-component dishes;
home-cooked meals;
restaurant dishes;
beverages;
desserts;
snacks;
soups;
salads;
dishes with sauces;
dishes with multiple ingredients;
packaged food;
partially eaten dish;
large and small portions;
photos with different lighting;
photos from above and at an angle;
blurry or darkened photos;
multiple dishes in one photo.
For each scan, it is necessary to check:
whether the dish is correctly identified;
whether the main ingredients are correctly identified;
how realistically the portion weight is determined;
how realistically the calories, proteins, fats, and carbohydrates are determined;
whether the result can be edited;
whether the result is correctly saved;
whether errors, freezes, or crashes occur in the application.
Laboratory verification of calorie accuracy is not required. It is necessary to assess whether the results appear logical and realistic.
Food diary
Editing products, portions, weight, calories, and macronutrients.
Adding food for past or future dates.
Switching between days.
Correctness of daily total calculation.
Correctness of displaying remaining calories and macronutrients.
Checking whether data is saved after closing and restarting the application.
Other functions
It is necessary to check all functions available in the current version of the application, including:
weight tracker;
adding, changing, and deleting weight;
graphs and statistics;
user goals;
changing personal data;
settings;
changing the language;
functionality after minimizing the application;
functionality after logging out;
data synchronization after re-login.
If other functions are discovered during testing, they must also be checked.
Negative and non-standard scenarios
It is necessary to try to trigger errors through non-standard actions:
rapid multiple pressing of buttons;
closing the application during loading;
disconnecting the internet during scanning or saving;
uploading a very large, small, or low-quality photo;
uploading a photo without food;
inputting text instead of numbers;
inputting zero, negative, or excessively large values;
multiple editing and deleting of data;
rapid switching between screens;
changing the date and time on the device;
re-login after deleting or reinstalling the application.
Testing duration
Testing should be conducted for at least 3–5 days.
During this period, the application should be used daily as a real user:
adding meals;
scanning dishes;
editing results;
adding weight;
viewing statistics;
checking data retention between sessions.
Report format
The results must be provided in the form of Google Sheets, Excel, or another agreed-upon table.
For each identified issue, the following must be specified:
Issue title.
Device and model.
Operating system version.
Application version.
Preconditions for occurrence.
Step-by-step reproduction scenario.
Actual result.
Expected result.
Frequency of occurrence.
Issue priority: Critical, High, Medium, or Low.
Screenshot or screen recording.
Each bug must have a separate entry. Phrasing like "not working" without description and reproduction steps will not be accepted.
Additionally, a table with the results of 50 dish scans must be provided:
dish name;
photo;
recognition result;
determined weight;
determined calories and macronutrients;
adequacy assessment of the result;
identified errors or comments.
Expected result
Upon completion of the work, we expect to receive:
a complete list of tested functions and scenarios;
a structured list of identified bugs;
screenshot and video recordings of issues;
results of scanning at least 50 different dishes;
a list of UX comments and unclear moments;
a brief overall conclusion regarding the stability and readiness of the application;
a list of the most critical issues that need to be fixed as a priority.
Requirements for the performer
Experience in testing mobile applications.
Availability of an iPhone or Android smartphone. The ability to test the application on both platforms will be an advantage.
Ability to clearly describe bugs and reproduction steps.
Ability to record screen videos.
Attention to detail.
Willingness to test the application over several days, not just once.
In your response, please indicate:
experience in testing mobile applications;
models of available devices;
versions of iOS or Android;
whether you can test both platforms;
an example of a formatted bug report;
an estimated cost for completing the entire task.
