Contact us
QA Audit for BedzAI mobile application

340+

Test cases

99%

Execution Coverage

82%

Pass Rate

Overview

BedzAI is a room and accommodation-finder app connecting agents/property owners who list rooms and bedspaces with guests searching for a place to stay. With two distinct user journeys running on a single production app — Agent-side listing and management, and Guest-side search and booking — BedzAI needed a structured, real-device QA pass on its live production build before scaling further. Testvox was brought in to run a full functional test cycle across both user flows on the production Android build, evaluating everything from registration and listings to messaging, notifications, and location-based search.

Challenges

Before working with Testvox, BedzAI faced three core testing challenges:

  • Two Parallel User Journeys Agent modules (listings, post history, earn & refer) and Guest modules (search, filters, room requests, saved alerts) needed independent validation while sharing core infrastructure like login, notifications, and messaging.
  • Location-Dependent Accuracy As a room-finder platform, incorrect city/region matching or broken location detection directly breaks the core value of the app — showing users the wrong listings in the wrong place.
  • Time-Sensitive User Journeys Messaging, notifications, and PIN-based account recovery are trust-critical flows; a silent failure here (like a missed message alert) has a disproportionate impact on user confidence compared to a cosmetic bug.

Testvox Solution

Testvox structured the engagement around real-device, production-build testing across both user roles:

  1. Requirement & Module Mapping

    2. Mapped test scope across 25 distinct modules spanning both Agent User flows (Registration, Post Listing, Settings, Messages, Room Requests) and Guest User flows (Smart Search, Filters, Session Management, Permissions), building a requirement coverage matrix per module.

  2. Test Case Design & Execution

    3. Designed and executed 340 test cases against the live production build (com.ai.bedzy) across real Android devices, achieving 99% execution coverage in a single test cycle.

  3. Defect Classification by Risk

    4. Logged 60 failures and rated each by priority and severity, isolating a small number of high-risk modules — Post Listing, Room Requests, Messages, and Settings — that accounted for a disproportionate share of critical and major defects.

  4. Cross-Device Validation

    5. Executed the full test suite across two device profiles (Vivo Android and Samsung Galaxy A55) to catch device-specific rendering and behavior issues alongside functional defects.

  5. Tiered Recommendations

    6. Organised findings into three clear action tiers — Fix Before Next Release, Fix Soon, and Low Priority — so BedzAI's engineering team could sequence fixes by real user impact rather than working through a flat bug list.

Result

Risk Prioritization

With Post Listing, Room Requests, and Messages flagged as the highest-density defect modules, BedzAI could focus engineering effort on the flows most likely to break a user's first experience with the app.

Release-Readiness Data

A 99% execution coverage figure against 340 test cases, paired with a full requirement coverage matrix, gave BedzAI a clear, quantified view of where the production build stood before further rollout.

Actionable Fix Roadmap

Rather than a raw defect list, BedzAI received a tiered roadmap — critical trust-breaking issues like broken notification deep-linking and non-functional PIN recovery flagged for immediate action, with lower-impact UI issues sequenced separately.

Conclusion

For a two-sided marketplace app, the flows that quietly fail — a notification that never fires, a location that resolves to the wrong city, a message button stuck loading — are often more damaging than visible crashes, because users simply stop trusting the app rather than reporting the problem. Testvox's structured, module-by-module testing gave BedzAI a clear, prioritized picture of where the production build stood and exactly what to fix first.

Related Resources