Manual QA for mobile application (iOS and Android)

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.

Für ein Kundenprojekt im Bereich Microsoft 365 Modern Workplace suchen wir erfahrene Freelancer (m/w/d) mit Schwerpunkt Microsoft Places. Im Mittelpunkt steht die Beratung, Konfiguration und Optimierung einer Microsoft-365-Umgebung zur Unterstützung moderner Hybrid-Workplace-Konzepte. Aufgaben Beratung bei der Einführung und dem Betrieb von Microsoft Places Analyse bestehender Microsoft-365-Umgebungen und Erarbeitung geeigneter Lösungskonzepte Konfiguration von Gebäuden, Stockwerken, Meetingräumen und Arbeitsplätzen Einrichtung und Optimierung von Desk-Booking- und Room-Booking-Szenarien Integration von Microsoft Places in Microsoft Teams, Outlook und Exchange Online Unterstützung bei Lizenzierungsfragen sowie Best-Practice-Empfehlungen Durchführung von Workshops und Know-how-Transfer für Anwender und IT-Teams Unterstützung bei Troubleshooting sowie im laufenden Betrieb Anforderungen Mehrjährige Erfahrung im Microsoft-365-Umfeld Praktische Erfahrung mit Microsoft Places Sehr gute Kenntnisse in Microsoft 365, Microsoft Teams, Exchange Online und Outlook Erfahrung mit Microsoft Entra ID (Azure AD) Kenntnisse moderner Hybrid-Workplace- und Modern-Work-Konzepte Wünschenswerte Kenntnisse Microsoft Teams Premium PowerShell für Microsoft-365-Administration Erfahrung mit Arbeitsplatz- und Raumbuchungslösungen Microsoft-Zertifizierungen im Bereich Modern Workplace oder Microsoft 365 Erfahrung in der Konzeption und Einführung moderner Arbeitsplatzkonzepte Start: asap Dauer: ca 3 Monate mit Option auf + Einsatzort: Remote / nach Absprache Auslastung: Nach Absprache Interesse? Da sich das Projekt aktuell in der Vorbereitungsphase befindet, möchten wir frühzeitig passende Experten kennenlernen. Bitte senden Sie uns an contract (AT) advergy de : CV Verfügbarkeit Stundensatz (Remote / Onsite) Dreizeiler, wieso Sie besonders gut auf das Projekt passen Vielen Dank und liebe Grüße Seda

We are interested not just in writing individual automated tests, but in building a quality foundation that can be scaled and maintained in the future.What we expect in the first stage a brief audit of the current testing process and testing environment; identification of critical user (UI/E2E) scenarios; recommendations for the automation stack and architecture of the testing project; setting up the project structure for automation; development of ready-made automated tests for critical user scenarios; documentation on launching, maintaining, and further developing the automated tests.Which scenarios we are interested in The first stage covers only the user part of the site: authorization; product catalog; search; product card; cart; checkout; personal account. API, integrations, and testing of the administrative part of Magento are not included in the scope of the project at this stage.What is important Experience specifically with Magento 2, e-commerce, or marketplace projects will be a significant advantage. In your response to the project, please indicate: experience with similar projects; examples of implemented automated tests or cases; which automation stack you recommend and why; what exactly will be included in the first stage of work; what deliverables we will receive after the completion of the first stage; the estimated number of automated tests that will be included in the first stage; the estimated budget and timeline for implementation. We are considering a long-term collaboration. If the first stage is successful, we plan to expand the coverage with automated tests and scale the approach to other e-commerce projects.

We are looking for an experienced QA partner or team to help build a testing process for an e-commerce project on Magento 2. At the first stage, we are interested not just in writing automated tests, but in a comprehensive approach to organizing QA. What needs to be done: conduct an audit of the current testing process; assess risks and identify critical user scenarios; provide recommendations for building the QA process; help determine which scenarios should be tested manually and which should be automated; suggest the optimal technology stack for automation; prepare an automation implementation plan; evaluate timelines, budget, and further support. At the first stage, we are specifically interested in automating user (UI/E2E) scenarios. The main business processes include product catalog, search, product card, cart, order placement, authorization, and user personal account. Experience with Magento 2, e-commerce, or marketplace projects will be a significant advantage. When responding to the project, it will be helpful to mention: experience with Magento 2; examples of similar projects; which automation stack you recommend (Playwright, Cypress, Selenium, etc.) and why; how you usually build the automation implementation process; an approximate approach to estimating work; who will work on the project (QA Lead, Automation QA Engineer, team). We are considering a long-term collaboration. If the first stage is successful, we plan to scale automation to other e-commerce projects.

About the project: We are developing a browser-based Web3 game on the blockchain: an interactive game world with a map, resource mining mechanics, wallet connection, on-chain transactions, and an internal economy. The project is in the active development stage. We are preparing a build for testing key systems before the next phase. Task: Conduct deep functional testing of the build — find and document bugs, vulnerabilities, and bottlenecks. The goal is not to "complete the game," but to break it: identify where the logic fails, where mechanics can be abused, where UX is poor, and where transactions are failing. Responsibilities: Testing wallet connection and functionality, authorization Verification of transactions and payments (on-chain + in-game) Testing game logic: map, mining, drops, interaction with the world Searching for vulnerabilities and abuse/fraud vectors in the economy and balances Load cases: mass actions, rapid clicks, behavior under load Cross-platform testing: PC and mobile browsers Clear documentation of bugs: reproduction steps, expected/actual results, screenshots, environment Requirements (mandatory): Experience in manual functional testing of web applications for at least 1 year Practical experience in Web3 as a user: wallets (MetaMask, Phantom, etc.), transactions, dApps — without this, wallet and on-chain testing is impossible Experience in game testing Understanding of how web applications work: HTTP, REST API, DevTools Ability to systematically search for bugs and describe them clearly Will be a plus: Experience in testing fintech/crypto products or transactions Working with Postman, test networks (testnet), blockchain explorers Familiarity with Solana Conditions: Format: one-time testing, remote Date: 15.07 Payment: negotiable (please specify your rate in the response) In your response, please include: Experience in QA + an example of an interesting/critical bug you found Your experience in Web3: which wallets you use, whether you have tested on-chain transactions Experience in game testing Your rate for this testing