- Centralized QA Review and Coordination
TestVox established a structured process where incoming ad-hoc requests were first reviewed by a QA Lead. The QA Lead verified:
Test case clarity,
Build accessibility and installation ,
Testing instructions from the Uber team ,
Any required clarifications were quickly coordinated with the Uber Point of Contact (POC)
before sharing the tasks with the testing team.
- Efficient Remote Test Execution
Once the test cases and builds were validated, they were shared with our testing team based in the United States.
The testers executed all provided test cases across the following builds:
Uber Ride Application – Android
Uber Ride Application – iOS
Uber Eats Application – Android
Uber Eats Application – iOS
Testers carefully followed the provided test scenarios and verified expected outcomes across the applications.
- Structured Evidence Documentation
To maintain full traceability of test execution:
Each test case execution was recorded using screen recordings.
The recordings were uploaded to a centralized drive repository.
The corresponding drive link was attached directly to the test case sheet.
Testers also updated the execution status and added comments, ensuring that stakeholders had complete visibility into the testing results.
- Transparent Reporting and Tracking
The test case sheet served as the central tracking document, capturing:
Test case execution status (Pass / Fail / Blocked)
Evidence links for verification
Tester observations and comments
This approach ensured clear traceability between test execution, results, and supporting evidence, enabling efficient review and feedback.