QA Tester / User Acceptance Testing (UAT) – PayEarth

Here is the exact updated text from Aadesh, formatted so you can copy and paste it directly into Upwork: Title: QA Tester / User Acceptance Testing (UAT) – PayEarth Job Description: We are looking for reliable QA testers / real-world users to thoroughly test our PayEarth web platform for one week before production release. PayEarth is a two-sided marketplace, so we need more than basic page testing. You will use the platform like a real user and identify functional bugs, workflow issues, UX problems, transaction issues, responsive issues, and edge cases. This is manual functional/UAT testing. No coding or automation is required. Testing Structure Each tester will be assigned one specific role: * Buyer/User * Seller * Admin You will test all pages, features, workflows, and functionality available for your assigned role. Because PayEarth is a two-sided marketplace, some workflows will also require coordinated Buyer/Seller testing to verify that actions, statuses, messages, and notifications are correctly reflected on both sides. What You Will Test Core Platform * Login, registration and logout * Profile/account * Dashboard * All role-specific pages * Navigation * Forms and validation * Create / Read / Update / Delete workflows * Search, filtering, sorting and pagination * Notifications * Chat and messaging * Modals and dropdowns * Loading, empty and error states * Settings and account functionality Transactional Workflows Where applicable: * Buyer/Seller interactions * Offers and orders * Order status changes * Checkout * Payments * Payment confirmation/history * Cancellations * Refunds * Seller transaction/payout workflows Cross-Role Testing Some workflows must be tested by two roles together. Example: Buyer → Seller * Buyer initiates an available transaction/workflow. * Seller receives it. * Seller takes the required action. * Buyer verifies the updated state. * Both users verify that information is consistent. Where real-time behavior is expected, verify: * Status updates * Chat/messages * Notifications * Order state * Whether unnecessary browser refreshes are required Coordinated testing sessions will be arranged when necessary. Payment Testing Use the provided Stripe sandbox/test environment only. Do not use real payment information. Where supported, test: * Successful payment * Card decline * Insufficient funds * Incorrect CVC * Expired card * Invalid payment details * Payment cancellation * Payment failure during checkout * Payment recovery * Order state after failed/successful payment * Partial/full refunds where available * Cancellation workflows * Multiple clicks on payment buttons * Refreshing during/after payment * Returning to the application after payment We want to verify both successful transactions and failure/recovery behavior. Multi-Tab & Concurrent Sessions Test real-world multi-session behavior where applicable: * Same account in multiple tabs * Mobile + desktop sessions * Actions in one tab reflected in another * Order/status synchronization * Chat synchronization * Notifications Example: perform an action in Tab A and verify whether Tab B updates correctly without unnecessary refresh where real-time behavior is expected. Network & Offline Testing Where possible, test: * Slow network * Slow 3G throttling * Temporary connection loss * Airplane mode * Reconnecting after going offline Pay particular attention to chat, payments, forms, uploads and order actions. The application should fail gracefully and clearly communicate when an action cannot be completed. Page-by-Page Testing Every accessible page for your assigned role must be tested. Check: * Correct page loading * Correct data * Loading states * Empty states * Error states * Buttons and links * Browser Back/Forward * Refresh behavior * Mobile responsiveness * Horizontal overflow * Cut-off/overlapping elements * Dropdowns and modals * Any errors affecting functionality CRUD Testing For every applicable feature, test the complete lifecycle. Create: Test valid data, missing required fields, invalid data, duplicates, long input and special characters. Read: Verify lists, details, newly created data, search and filters. Update: Edit individual and multiple fields, save, refresh and verify persistence. Delete: Test deletion, confirmation, cancellation, removal and persistence after refresh. Forms Test: * Required/optional fields * Empty submission * Invalid values * Incorrect formats * Long input * Special characters * Duplicate values * Cancel/Submit * Validation messages Validation should be clear and understandable to a normal user. Chat Thoroughly test: * Existing conversations * New conversations * Sending messages * Short/long messages * Multiple messages * Emojis * Attachments where available * Message deletion where available * Blocking users * Switching conversations * Empty conversations * Refresh * Mobile chat * Sidebar * Back navigation * Notifications/unread behavior * Profile images/initials * Loading states Pay particular attention when switching conversations. Messages from one conversation must never temporarily appear in another. For complex chat issues, provide a screen recording. Authentication & Navigation For your assigned role, test: * Login/logout * Invalid credentials * Session persistence * Refresh after login * Browser Back after logout * Protected pages * Unauthorized access where applicable * Mobile login/logout * Profile dropdown * Role/mode switching where available Also test header, sidebar, dropdown, breadcrumb, logo, internal links and browser navigation. UI/UX Testing Report issues even when functionality technically works. Look for: * Poor alignment * Inconsistent spacing * Cut-off text * Confusing buttons/labels * Small tap targets * Poor dropdown/modal positioning * Unclear error messages * Missing empty states * Excessive loading * Unexpected scrolling * Horizontal overflow * Overlapping elements * Desktop/mobile inconsistencies If something works but is unnecessarily difficult or confusing, report it as a UX improvement. Edge Cases Try scenarios such as: * Double-clicking/repeatedly clicking buttons * Rapid page switching * Rapid chat switching * Refreshing during loading * Back while modal/dropdown is open * Repeatedly opening/closing modals * Very long names/messages * Missing profile images * Empty lists * Slow/lost network Mobile & PWA Testing Test on real mobile devices where possible. Check: * No horizontal scrolling * No blank space on the right * No layout shifting * Stable header * Sidebar * Dropdowns * Modals * Keyboard behavior * Chat composer * Chat scrolling * Back navigation * Portrait/landscape * PWA behavior 7-Day Testing Schedule Days 1–2: Core Platform Account flows, profiles, dashboards, navigation, catalog/listings, search, filtering, sorting, forms and CRUD. Days 3–4: Interactive & Transactional Buyer/Seller workflows, chat, offers/orders where available, order states, checkout, Stripe sandbox payments, payment failures/recovery, refunds/cancellations and real-time synchronization. Day 5: Mobile, PWA & Stress Testing Real devices, PWA, portrait/landscape, slow/offline network, multi-tab, concurrent sessions, edge cases and mobile navigation. Days 6–7: Regression & Final QA Re-test fixed bugs, verify no regressions, repeat critical workflows and perform final UX/UI review. Bug Reporting All issues must be recorded in the provided shared testing tracker. Each report should include: * Bug title * Tester * User role * Page/feature * Device * Browser * Steps to reproduce * Expected result * Actual result * Severity * Screenshot/evidence For chat, payment, multi-step workflows, real-time synchronization or difficult-to-explain UI issues, screen recording is required whenever possible. Daily Report At the end of each day, provide: * Day: * Pages Tested: * Features Tested: * Bugs Found: * UX Improvements: * Cross-Role Tests Completed: * Blocked / Unable to Test: Do not simply report "everything works." Clearly document what was actually tested. Important Rules * Test thoroughly; do not stop after finding one issue. * Report all relevant issues. * Do not assume confusing behavior is intentional. * Avoid duplicate reports. * Test both success and failure scenarios. * Use designated test accounts/data. * Never use real payment information. * Provide screenshots and recordings when appropriate. Most Important Principle Think like a real customer, not a developer. Don't ask: "Does this technically work?" Ask: "If I were a real PayEarth user, could I complete this task easily, correctly, and without confusion?" If the answer is no, report it. Duration: 1 week Type: Manual QA / User Acceptance Testing Requirements: No coding or automated testing required