Damilola Oludayo
QA Engineer for Early-Stage Startups | Web, Mobile & Web3
Ready for work
Damilola is ready for their next project!
🧪 Recent QA Insight:
Even “simple” login flows can hide issues:
Too-short password reset links
Missing loading states on slow connections
Mobile keyboard covering buttons
Exploratory testing caught all of them.
Always worth going beyond the checklist.
🧪 Quick Real-World QA Example:
Recently spotted a checkout flow issue on mobile with saved addresses:
Silent validation failure
Disabled payment button
Poor error feedback
A single exploratory test caught it quickly.
These kinds of hidden problems are exactly why dedicated testing...
Not every bug is obvious.
I was testing a registration flow where everything worked perfectly over Wi-Fi.
The same login failed consistently when using mobile data.
The issue wasn’t the login screen—it was how the app behaved under different network conditions.
Bugs like these are...
One network.
One login.
Two very different results.
Wi‑Fi passed.
Mobile data exposed a login issue.
Sometimes the environment is the test case.
I don't enjoy finding bugs.
I enjoy finding them before users do.
Big difference.
A bug found during testing is a task.
A bug found by a customer is a problem.
That's why QA matters.