May26- Master Bug Tester Notifications $60 per Bug - Software Notification Module Tester - Ongoing

@Microlent

Hi, Testing the GPI money transfer parameters and the matching logic between User A and User B needs a very specific mindset. I see how critical it is for the system to automate these deals so buyers and sellers do not have to hunt for offers manually. If the email notifications fail, the platform loses its primary value. I will set up multiple accounts to verify the instant, daily, and weekly schedules. My process ensures every bug report includes the exact Loom video and category preferences required. I will catch why a matched offer might not trigger an email even after the fifteen minute wait period. You can see my experience with detailed defect logging here: https://www.freelancer.com/portfolio-items/11354470-software-qa-testing-report I am ready to start testing the request notifications and cross-user matching logic immediately. Let's kick off with a small milestone for Cross-user notification logic testing. You only release when you're happy. ~ Rajesh

@Tanmoy236

I am ready to start and I have read all specs ! I know and have seen where is the members my notifications module/area. I specialise in QA and functional testing of notification systems, including email-trigger validation, rule-based matching logic, and multi-user workflow testing across complex role scenarios. Here’s how I will approach your testing: • Create multiple users (A, B, C) and configure category/sub-category preferences exactly as described • Generate matching offers and requests across different scenarios to validate both Case 1 (buyer-side matching) and Case 2 (provider-side matching) • Verify email delivery timing (instant / scheduled / weekly) and confirm correct payload content per rule set • Document every unique functional bug with full reproduction steps, screenshots of User A preferences, User B/C trigger data, and email proof (or missing delivery evidence via inbox + logs) • Package each confirmed issue into separate ZIP files as required, ensuring no duplication of bugs across categories Before I begin, I only need 3 quick clarifications: 1. Do you have a staging environment or should I test directly on production with test accounts? 2. Where can I access email delivery logs (SMTP, admin panel, or third-party service like SendGrid/Mailgun)? 3. Is there a fixed waiting window per test case before marking “email not received” as a bug (e.g., 10–15 minutes per your note, or longer for scheduled batches)?

@zainulhassan1695

Hi, I AM READY TO START AND I READ ALL SPECS ! I KNOW AND HAVE SEEN WHERE IS THE MEMBERS MY NOTIFICATIONS MODULE/AREA. I understand the testing flow for both Offers notifications and Requests notifications using multiple registered users (User A, User B, User C, etc.) with different category/subcategory preferences and transaction parameters. I will: - Configure notification preferences for User A - Create matching offers/requests using other accounts - Wait for instant/daily/weekly notification timing before reporting - Verify whether correct emails are received or missing - Check for wrong matching logic, missing notifications, duplicate emails, incorrect data, and preference mismatches - Test multiple categories/subcategories and different parameter combinations - Provide each logical functional bug in its own ZIP file with: - Screenshot evidence - Text explanation - Loom video if needed - User A preferences - User B/C submitted offer or request - Email proof and reproduction details I understand this is notification logic testing only, not dashboard UI testing, and I am ready to begin immediately.

@hareshfinadiya

Hi, I am Haresh, having 14+ years of experience in Software Testing Industry. - Having unique blend of knowledge in Quality Product Delivery, Processes Management, Functional testing, Integration and regression testing, load and Perfromance Testing which help me to take the Quality of the software to the next level. - Hands on experience on testing Desktop, Web Based, Mobile application and ERP based application. - Hands on experience on automation testing tools on selenium webdriver, jmeter, katalon studio, Appium, cypress, selenium with TestNG freamwork etc.. - Thorough understanding of Product Delivery Life Cycle, Software Testing Life Cycle and Software Development Life Cycle. - Experience in Well conversant with writing Test plan,Test Cases,Bug report, Release Note and Product Health Report. - Worked in various domains like Finance, Retail, Web Portals, Healthcare, ecommnerce, CMS, Eduction Portal, Life Insurance, ERP system etc. - I do have require mobile devices to test mobile view or applications like android and iOS applications. - I have hands on experience with Git, postman, MSSQL Server. Kindly review my profile and let me know you view over the same. Thanks, Haresh

@ZohaibRoy

⭐⭐⭐⭐⭐ Bug Tester for Notifications Module in Software Marketplace ❇️ Hi My Friend, I hope you are doing well. I've reviewed your project details and see you are looking for a Bug Tester for the Notifications Module. You need not look any further; Zohaib is here to help you! My team has successfully completed 50+ similar projects focused on testing software modules. I will thoroughly test the notifications system by setting various user preferences and submitting offers or requests to ensure everything works correctly. ➡️ Why Me? I can efficiently test your Notifications Module as I have 5 years of experience in software testing, focusing on bug identification and reporting. My expertise includes functional testing, regression testing, and user acceptance testing. Additionally, I have a strong grip on various testing tools and methodologies, ensuring a thorough and effective approach to your project. ➡️ Let's have a quick chat to discuss your project in detail. I can provide samples of my previous work, showcasing my experience in software testing. Looking forward to discussing with you! ➡️ Skills & Experience: ✅ Software Testing ✅ Bug Reporting ✅ Functional Testing ✅ Regression Testing ✅ User Acceptance Testing ✅ Test Case Development ✅ Test Automation ✅ Email Notification Testing ✅ Quality Assurance ✅ Documentation Skills ✅ Attention to Detail ✅ Problem Solving Waiting for your response! Best Regards, Zohaib

@ManniDani

I will thoroughly audit your notification system to ensure prompt delivery, real-time sync, and perfect trigger accuracy. With 5+ years of QA experience testing high-stakes communication workflows for Citibank, I know exactly how to spot hidden synchronization flaws. I’ll provide clear, actionable bug reports with precise reproduction steps so your team can ensure users never miss a beat. Let's make it flawless!

@dorisnst

Hi, I AM READY TO START AND I READ ALL SPECS ! I KNOW AND HAVE SEEN WHERE IS THE MEMBERS MY NOTIFICATIONS MODULE/AREA. I am ready to begin testing immediately. Best regards, Doris

@patricko098

I recently completed a detailed bug testing project for a notification system that improved notification accuracy by 30 percent and simplified issue tracking. I am new to Freelancer but have worked on large projects involving notification systems at companies like Google and Stripe, which gave me solid experience in testing complex software modules under real-world conditions. I understand you need thorough testing of your notifications module to ensure clean, seamless, and efficient matching between users’ offers and requests based on category preferences, with reliable email delivery of those notifications. I work with clear structure and simplicity, focusing on building testing processes that find real issues early while avoiding unnecessary complexity, ensuring long-term reliability. I am ready to start testing your notifications module following your specifications. If this aligns with your project, feel free to reach out to discuss scope and pricing. Regards Patrick

@ZainShah22

I AM READY TO START AND I READ ALL SPECS ! I KNOW AND HAVE SEEN WHERE IS THE MEMBERS MY NOTIFICATIONS MODULE/AREA. I understand the full notification matching workflow for both Offers and Requests, including testing category/subcategory preferences, instant/daily/weekly email triggers, and validating correct matching behavior between User A and Users B/C. I will create multiple users, test different scenarios, wait the required 10–15 minutes for notification delivery, and provide each logical bug in its own ZIP with screenshots/Loom evidence, preferences setup, matching offers/requests, and proof of incorrect or missing emails.

@ayesha86664

Hi there! Notifications not triggering correctly or sending wrong matches can seriously break trust in a marketplace system. These issues often come from logic errors in preference matching, scheduling, or email queue handling. I have strong experience in QA testing for web applications, especially workflow-based systems like marketplaces and notification engines. I have tested email automation systems, user-role based workflows, and preference-driven matching logic in complex platforms. I am also experienced in identifying functional bugs, reproducing them clearly, and documenting them with proper proof and steps. My approach will be to carefully create multiple test users and simulate real scenarios as described in your system. I will set different preferences for User A and generate matching and non-matching offers/requests from User B and C. I will verify email delivery timing, correctness of matching logic, and identify where the system fails. Each bug will be documented separately with clear steps, screenshots, and email evidence as required. check our work https://www.freelancer.com/u/ayesha86664 Can you confirm if email delivery is instant or batch-processed with delay for your notification system? Let me know if you’re interested & we can discuss it. Best Regards Ayesha

@chinmayees10

I AM READY TO START AND I READ ALL SPECS ! I understand the full notifications testing flow and I know I need to test ONLY the email notification matching system — not the dashboard display. I understand: • User A sets notification preferences by category/subcategory • User B/C create matching offers or requests • I wait 10–15 minutes and verify whether User A receives the correct instant/daily/weekly email notifications • I must test both OFFERS and REQUESTS workflows • Each logical bug will include: User A preferences screenshots User B/C matching offer/request screenshots Email inbox proof (missing email or incorrect email data) Reproduction steps Loom/screenshots Separate ZIP file per bug I also understand duplicate bugs are not acceptable and different categories/subcategories should be tested. i know and have seen where is the members my notifications module/area.

@kunalk229

I AM READY TO START AND I READ ALL SPECS ! I KNOW AND HAVE SEEN WHERE IS THE MEMBERS MY NOTIFICATIONS MODULE/AREA. I have 1 relevant question before starting: 1. Should I create all test accounts using separate email inboxes, or can aliases under one email domain be used for User A, User B, and User C for notification validation? I will test both Offers and Requests notification flows with multiple category/subcategory combinations, verify Instant/Daily/Weekly matching behavior, and submit each unique logical functional bug separately with: - User A preferences screenshots - User B/C matching offer or request screenshots - Email evidence (received / not received / wrong match) - Loom or screenshots - Separate ZIP file per bug as requested I will avoid duplicate bug reports and wait the required 10–15 minutes before reporting notification delivery failures.

@sabaehsan

Greetings, I’m ready to start and I read all specs! I know and have seen where the members' notifications module is located. It looks like you need someone to thoroughly test the software's notifications module by setting up different user preferences and verifying if the expected email notifications are sent out correctly. I will register multiple users and set specific preferences for each to test various categories and subcategories. By submitting offers or requests under different usernames, I will check if the notifications align with the preferences set for each user. My focus will be on identifying logical bugs and documenting them clearly, including screenshots and Loom recordings if necessary. With my attention to detail and experience in software testing, I’m confident I can help ensure everything runs smoothly. Best regards, Saba Ehsan

@mayr81

Hi there, I’m ready to start and I read all specs! I know and have seen where is the Members / My Notifications module/area. I’ll register multiple free users (User A for the tested preferences, plus User B/C to submit matching Offers and Requests) without testing the dashboard display, only the notification emails after preference changes and different schedule settings. For each notifications bug, I’ll provide a separate zip with: User A preferences screenshots, the exact Offer/Request submitted by User B (or C), and the email evidence (Loom or screenshots) showing whether User A received the matched notification within 10-15 minutes and whether the content matches the selected category/subcategory and parameters. I’ll cover both logic paths: (1) matched Offers sent to the receiver/buyer/investor based on category/subcategory and offer parameters, and (2) matched Requests sent to providers/senders even when the offer isn’t posted yet. I will avoid duplicate reports and will test multiple distinct categories/subcategories and request/offer parameter sets to uncover functional matching errors. Do you want me to prioritize instant vs daily/weekly first?

@SidUSA

Hi, We are available to start and we read all specs! We know and have seen where is the members my notifications module/area. We can systematically test your software marketplace notifications module, focusing entirely on email delivery based on category and subcategory settings. We will configure User A's preferences for both Case 1 (Offers matched to buyers) and Case 2 (Requests matched to providers), trigger the events using separate user accounts, and allow the necessary time for email processing. For every logical functional bug discovered, we will provide an isolated ZIP file containing the required documentation: User A's specific preference settings, the matching offer/request from the secondary user, and a Loom video or screenshot proving the email delivery failure or data mismatch. We accept the $60 per bug rate and the initial $180 milestone. Best regards, Quantum Code Solutions

@GenePauly

Hi there, This is Gene from Luxembourg. I already understand the core issue here because notification matching systems usually fail around preference normalization, delayed queue processing, category inheritance, or request/offer direction mapping between sender and receiver flows. I’ll test both instant and scheduled notifications using multiple user roles across different category/subcategory combinations and document only real logical matching bugs with separate ZIP evidence including preferences, matching offers/requests, and missing or incorrect emails. I’ve worked on high-concurrency notification and messaging systems at LiveJasmin and complex user flow platforms at Oranum where preference-driven delivery logic and edge-case testing were critical. I can start immediately and deliver first verified bugs within 1 day. I AM READY TO START AND I READ ALL SPECS ! I KNOW AND HAVE SEEN WHERE IS THE MEMBERS MY NOTIFICATIONS MODULE/AREA

@vijaydogra03

Hello, I have read your full specifications carefully and I understand exactly what you need for the Notifications Module testing. My Approach I will perform systematic functional testing of your notification engine: Setup Phase Register multiple test accounts (User A, B, C) Configure different notification preferences per user Map test cases across categories and subcategories Execution Phase Create matching and non-matching offers/requests Trigger system events (transactions, offers, requests) Wait for configured notification intervals (instant / scheduled 10–15 mins / daily/weekly) Verification Phase Validate email delivery for User A Confirm correctness of matching logic Check missing emails, incorrect matches, or duplicate triggers Compare expected vs actual behavior Bug Reporting Format (Each Bug in Separate ZIP) I will ensure each bug is unique and properly validated before reporting, as per your instructions. I am ready to start immediately after access is provided. I understand the workflow, the notification module behavior, and the expectation of structured bug reporting with proof. I am ready to start and I read all specs! I know and have seen where is the members my notifications module/area. Best regards, Vijay.

@igorn43

I AM READY TO START AND I READ ALL SPECS ! I KNOW AND HAVE SEEN WHERE IS THE MEMBERS MY NOTIFICATIONS MODULE/AREA.

@chrissiebosman

I AM READY TO START AND I READ ALL SPESCS ! I KNOW AND HAVE SEEN WHERE IS THE MEMBERS MY NOTIFICATIONS MODULE/AREA. I will fully test the notifications module using multiple registered users (User A, B, C, etc.) for both Offers and Requests scenarios across different categories and subcategories. I will verify: Instant / Daily / Weekly notification delivery Correct category & subcategory matching Email delivery failures Wrong or unrelated notification data Buyer/Seller matching logic Requests notifications to providers Offers notifications to buyers/investors For every bug found I will provide: User A preferences screenshot User B/C matching offer or request screenshot Email inbox proof with Loom or screenshots Clear reproduction steps Separate ZIP file for each logical functional bug I understand duplicate bugs are not accepted and I will test different combinations and parameters carefully before reporting. Ready to start immediately.