QA Case Study on My Ulo
Software quality is often measured by what users never experience; broken features, confusing workflows, security issues, and application crashes. As a Quality Assurance Engineer, my responsibility is to identify and eliminate these issues before a product reaches users.
In this article, I share my experience testing My Ulo, a property rental platform designed to help Nigerians find verified rental properties while reducing the risk of rental scams. This project challenged me to test an MVP independently while ensuring that the application's most important user journeys functioned reliably across the web and Android platforms.
Project Overview
Project: My Ulo
Duration: One Month
Role: QA Engineer
Team Size: One QA Engineer- OKOYE GLORIA CHINWENDU.
Platforms Tested: Web and Android
The primary objective of the project was to validate an MVP that introduced several important features, including verified property listings, mock identity verification, GPS-based reviews, interactive maps, video walkthroughs, and a mock payment workflow.
Because the application aimed to improve trust within the property rental market, ensuring the reliability of these features was critical. A defect in authentication, property verification, location services, or payment flow could significantly affect user confidence in the platform.
Understanding the Product
The Nigerian rental market presents several challenges for prospective tenants, including fraudulent property listings, inaccurate location information, and difficulties verifying landlords or agents.
My Ulo attempts to address these challenges by combining property verification with location-based features and structured user workflows.
The platform allows users to:
- Register and log into the application.
- Browse verified rental listings.
- Search and filter available properties.
- View property locations on interactive maps.
- Watch video walkthroughs before scheduling inspections.
- Complete a mock payment process.
- Leave GPS-based reviews for properties.
- Support onboarding for landlords and agents.
- Provide administrators with tools to manage platform activities.
Every one of these features required careful validation to ensure users could complete their intended tasks without confusion or unexpected failures.
My QA Strategy
Since I was the sole QA Engineer on the project, creating a structured testing approach was essential.
Rather than immediately executing tests, I first planned the testing activities to ensure complete coverage of the application's requirements. A well-defined testing strategy minimizes missed scenarios and improves overall product quality.
My QA documentation included:
- Test Execution Report: https://docs.google.com/document/d/1TnmbZua8YDzkyMAVNSIBFZj65Is3aAwK/edit?usp=drivesdk&ouid=103969217641706033370&rtpof=true&sd=true
- Bug report: https://docs.google.com/document/d/1QRSLQ8FD99oc_BuVUqWeOkEpd7YHNg-Y/edit?usp=drivesdk&ouid=103969217641706033370&rtpof=true&sd=true
- QA signoff: https://docs.google.com/document/d/19vNshmB4cCx-mvYtUBxwP9cleoCHISlQ/edit?usp=drivesdk&ouid=103969217641706033370&rtpof=true&sd=true
I also adopted a risk-based testing approach, prioritizing the application's most critical user journeys before testing lower-risk functionality.
This ensured that essential workflows such as authentication, property search, verification, and payments received the greatest attention throughout the testing process.
Defining the Testing Scope
To achieve broad coverage, testing focused on the application's major functional areas.
User Authentication
Authentication forms the foundation of every user experience.
Testing included validating user registration, login functionality, session behavior, input validation, and error handling to ensure users could securely access the platform.
Property Search and Filtering
Searching for rental properties is one of the application's primary user journeys.
Testing verified that filters returned accurate search results and that users could locate properties using the available search options without inconsistencies.
Property Listings
Each property listing was validated to ensure important information displayed correctly and consistently throughout the application.
The accuracy of listing information directly contributes to user trust.
Video Walkthroughs
Video walkthrough functionality was tested to confirm that uploaded videos displayed correctly and contributed positively to the property viewing experience.
Interactive Maps
Location information is essential in a rental application.
Testing ensured that maps loaded correctly and accurately represented property locations, helping users understand where properties were situated.
Mock Payment Flow
Although payment processing was simulated, the workflow still required complete validation.
Testing confirmed that users could progress through the payment process without interruptions while ensuring expected application behavior throughout the journey.
GPS-Based Reviews
One of the platform's unique features was restricting reviews based on GPS validation.
Get That AI Blog’s stories in your inbox
Join Medium for free to get updates from this writer.
Testing focused on verifying that review functionality behaved according to the application's location requirements.
Agent and Landlord Onboarding
Testing ensured that onboarding processes for property owners and agents functioned correctly and collected the required information.
Admin Dashboard
Administrative functionality was validated to ensure platform management features worked as intended and supported operational activities.
Types of Testing Performed
Achieving confidence in software quality requires combining multiple testing techniques rather than relying on a single approach.
For this project, I executed several forms of manual testing.
Functional Testing
Functional testing verified that every feature behaved according to the documented requirements.
This included validating expected outputs for different user actions while ensuring business rules were correctly implemented.
User Interface Testing
The user interface was evaluated to confirm consistency, readability, navigation, and overall usability across the application.
A visually appealing interface must also be intuitive and predictable.
Exploratory Testin
Exploratory testing allowed me to investigate the application beyond predefined test cases.
By interacting with the product from a user's perspective, I was able to uncover defects that structured testing alone might not reveal.
Regression Testing
Whenever issues were resolved, regression testing ensured that previously functioning features continued to work correctly after changes were introduced.
This reduced the risk of new defects being introduced during development.
Security Testing
Basic security-focused validation included reviewing authentication workflows and ensuring sensitive functionality behaved appropriately under expected conditions.
Compatibility Testing
Compatibility testing was performed using Google Chrome to confirm that application functionality remained stable within the supported browser environment.
Performance Checks
Basic performance observations ensured important pages and workflows responded appropriately and provided a satisfactory user experience.
Defect Management
Finding defects is only one aspect of Quality Assurance.
Equally important is documenting issues clearly so developers can reproduce and resolve them efficiently.
Every reported defect included:
- Clear title
- Severity
- Priority
- Test environment
- Preconditions
- Reproduction steps
- Expected result
- Actual result
- Supporting screenshots
- Resolution status
Maintaining consistent defect reports improved communication and simplified issue tracking throughout the project lifecycle.
Tools Used
To manage testing activities effectively, I used the following tools:
- ClickUp for project management and defect tracking.
- Microsoft Word for QA documentation and test artefacts.
- Google Chrome for browser testing.
Results
The testing effort produced measurable outcomes that demonstrated comprehensive coverage of the application.
Project metrics included:
- More than 165 test cases created.
- 158 test cases executed successfully.
- 95% requirements coverage achieved.
- 68 defects identified and reported.
- 100% of critical defects resolved before release.
- Zero blocker defects remaining at final testing sign-off.
These results reflected both thorough test planning and consistent execution throughout the project.
Conclusion
Working as the sole QA Engineer on My Ulo reinforced the importance of structured testing, comprehensive documentation, and risk-based prioritization.
Testing is much more than executing predefined test cases. It involves understanding user behaviour, anticipating edge cases, documenting issues effectively, and ensuring every critical workflow performs reliably before release.
This project demonstrates how a disciplined manual testing process can significantly improve product quality, even within a relatively short development timeline.
As I continue growing in Quality Assurance, projects like My Ulo remind me that quality is built through careful planning, thorough execution, and continuous attention to detail long before users ever interact with the final product.
