Mobile App Tester / Manual QA — Pre-Release Testing

# Automotive Marketplace App Tester / Manual QA — Potential Long-Term Work We are looking for an experienced and reliable **Mobile App Tester / Manual QA Freelancer** to thoroughly test our **automotive marketplace app** before release. This is hands-on, real-user testing. You will download the app onto a real mobile device and use it like a genuine customer — creating vehicle ads, browsing listings, creating stories, messaging other accounts, contacting support, managing your profile and testing as much of the app as possible. ## Marketplace Testing Experience Required You should understand how marketplace apps work from both sides: **Seller → Creates, publishes and manages vehicle listings** **Buyer → Searches for vehicles, views listings and contacts sellers** Experience testing **automotive marketplaces, classified apps, general marketplaces, e-commerce apps or similar platforms** is strongly preferred. We do not want someone who needs step-by-step instructions for every action. You should be comfortable exploring an app independently, thinking like a real buyer and seller, trying different scenarios and actively looking for things that don't work correctly. ## The Testing Session The initial job will be approximately **4–5 hours of active testing**. Your goal is to use as much of the app as possible during this time and complete **as many realistic actions as reasonably possible**. Quality is important, but we also want a high level of activity throughout the testing session. ## Accounts & Onboarding You will: * Download and install the latest version of the app * Create multiple test accounts * Test registration * Test login and logout * Complete onboarding * Edit profiles * Change account information * Test settings * Switch between different test users * Close and reopen the app during different stages ## Vehicle Ads / Listings A major part of the testing will involve creating vehicle advertisements. You should create **as many realistic vehicle ads as reasonably possible during the testing session**. We expect a high volume of testing rather than creating only a few listings. Listings should be varied rather than simply creating identical ads repeatedly. Test different: * Vehicle makes * Models * Years * Prices * Mileage * Descriptions * Photos * Vehicle specifications * Categories * Locations * Other available listing options Test the full seller journey: **Create → Publish → View → Edit → Manage → Buyer Interaction** Check that listings display correctly after being published and that other accounts can find and interact with them. ## Buyer Testing Act like someone genuinely looking to purchase a vehicle. Test: * Browsing vehicle listings * Searching for vehicles * Search results * Filters * Different search criteria * Opening listings * Viewing vehicle photos * Reading vehicle information * Viewing seller information * Contacting sellers * Sending messages * Returning to previous searches * Saved/favourite functionality if available * Whether newly created listings appear correctly Try different buyer journeys rather than repeating exactly the same actions. ## Seller Testing Act like someone genuinely selling vehicles. Test: * Creating vehicle ads * Uploading photos * Entering vehicle information * Publishing listings * Viewing live listings * Editing listings * Managing listings * Responding to potential buyers * Checking messages * Checking notifications * Changing listing information * Testing any other seller functionality available ## Messaging Messaging between buyers and sellers is an important part of the testing. You should: * Start conversations from vehicle listings * Send messages between different accounts * Reply from seller accounts * Reply from buyer accounts * Send multiple messages back and forth * Test multiple conversations * Test read/unread behaviour * Check that messages appear under the correct conversation * Check that conversations relate to the correct vehicle * Test notifications where available * Try unusual messaging behaviour where appropriate ## Stories You will also thoroughly test the Stories functionality. This includes: * Creating stories * Creating multiple stories * Viewing stories from other accounts * Playing/watching stories * Moving between stories * Testing interactions * Checking loading * Checking playback * Looking for visual problems * Testing stories between different accounts Create and interact with **as many realistic stories as reasonably possible** during the testing session. ## Customer Support You must also test the customer support functionality like a genuine customer. This includes: * Opening the Support/Help section * Sending support messages * Submitting support requests * Testing contact forms * Sending different types of enquiries * Checking confirmation messages * Checking error messages * Testing the support journey from beginning to end Do not ignore support simply because the main marketplace functionality is working. ## Try to Break the App We do not want someone who only tests the obvious happy path. Actively try to find problems. Examples include: * Leaving information blank * Entering incorrect information * Using very long text * Using unusual characters * Uploading different photos * Rapidly changing screens * Repeating actions * Editing something immediately after creating it * Switching between accounts * Sending multiple messages * Creating many listings * Creating multiple stories * Going backwards during a process * Closing and reopening the app * Trying actions in unusual orders * Testing what happens with poor or interrupted connectivity where practical * Repeating important user journeys Think independently. If you notice a feature we haven't specifically mentioned, **test it**. Our goal is to find problems **before our real customers find them**. ## What We Expect During the 4–5 Hours We want you actively testing throughout the session. Do not stop after completing a basic checklist. Once you have tested something successfully, try another scenario. Create more ads. Create stories. Browse as a buyer. Switch accounts. Message sellers. Reply to buyers. Use support. Edit listings. Change profile information. Search again. Try different filters. We want to get **as much useful testing coverage as possible** from the session. However, do not create hundreds of identical actions simply to increase numbers. Testing should remain realistic and useful. ## Bug Reporting Every meaningful bug should be clearly documented. For each bug, provide: **Bug title:** Short description of the problem **Device:** Phone model and operating system/version **Steps to reproduce:** Exactly what you did before the problem occurred **Expected result:** What should have happened **Actual result:** What happened instead **Evidence:** Screenshot or screen recording whenever possible Please make your bug reports detailed enough that our development team can reproduce the problem without having to ask you what happened. ## Payment **Fixed price: €75** Expected workload: approximately **4–5 hours of active testing**. This is initially a pre-release testing job rather than a full-time position. ## Potential Long-Term Work Although this is initially one testing session, **this could become a long-term working relationship if you are good**. We regularly need reliable people who can thoroughly test releases. If you: * Find useful bugs * Test thoroughly * Work independently * Communicate clearly * Complete a high amount of useful testing * Provide good screenshots/screen recordings * Write clear bug reports * Are reliable ...we would be happy to consider you for **ongoing testing before future releases**. We would prefer to find one excellent tester we can continue working with rather than finding someone new every time. ## Short Introduction Video Required Please include a **short 1–2 minute introduction video** with your application. The video does NOT need to be professionally produced. A simple phone or webcam recording is completely fine. Please briefly tell us: * Your name * Your QA/mobile testing experience * Any marketplace, automotive, classified or e-commerce apps you have tested * What phone/device you will use to test our app * How you would approach testing an automotive marketplace * Why you would be a good person for us to work with long term We mainly want to understand your **communication skills, experience and approach to testing**. ## Screening Questions **1. What marketplace, classified, automotive or e-commerce apps have you previously tested?** Please explain what you personally tested rather than simply listing app names. **2. Imagine we give you an automotive marketplace app with no detailed testing script. What are the first 10 things you would test?** Please be specific. **3. A seller successfully publishes a vehicle listing, but another account cannot find that vehicle in search. How would you investigate and report this problem?** **4. How would you test messaging between a vehicle buyer and seller?** Give several examples of scenarios you would test. **5. How would you test the process of creating a vehicle advertisement?** Include both normal scenarios and unusual/edge-case scenarios. **6. What smartphone(s) will you use for testing?** Please include the exact phone model and operating system/version. **7. During 4–5 hours, how would you divide your time between creating ads, browsing/searching, stories, messaging, support and general exploration?** **8. Are you comfortable creating a high volume of realistic vehicle ads/content and completing as many useful testing actions as possible during the session?** **9. Are you comfortable with the €75 fixed payment for approximately 4–5 hours of active testing?** **10. Please provide your short 1–2 minute introduction video.** Finally, start your proposal with the words: **AUTO TEST** This lets us know you have read the complete job description. Please do not apply if you are only interested in automated testing. We specifically need someone who enjoys **manually exploring and testing marketplace apps like a real buyer and seller** and who can independently find issues without needing instructions for every action. **Excellent performance can lead to regular long-term testing work with us.**