TapFlow
Android test recorder that auto-generates TestNG/POM Java test suites
The test automation bottleneck
At Bizom, every new Android feature needed a matching UI test suite. Developers were hand-writing TestNG tests by reading layout XML and tracing element hierarchies — 4–8 hours per suite, generating brittle code that broke on minor UI changes. QA velocity was less than half of development velocity. The ask was clear: automate the boilerplate.
Context
- 4–8 hours per test suite written manually
- High breakage rate — tests failed on minor UI changes
- No structured recording tool for Appium-based Android apps
- 12-week internship deadline
Our approach
Key decisions
Appium UIAutomator2 for element capture
Locators pulled from the actual accessibility tree, not fragile XPath. Tests survive UI refactors because they target semantic attributes, not coordinates.
Page Object Model generation
Generated full POM classes per screen, not flat test scripts. Future maintainers can extend tests without touching the framework.
Claude API for action naming
Used Claude to infer what each recorded action meant semantically — "tap Sign In button" vs "tap element at 340,890". Methods are readable, not coordinate dumps.
Zero-config TestNG runner
TestNG XML generated automatically. Developer runs one command — no manual Appium config, no boilerplate, no setup guide.
Results
What we achieved
Less time writing tests
Per suite (down from 4–8 hrs)
Internship delivery
QA pipeline in production
Stack used
Next project
RetailMind →Start a project
Let's build something great
Drop your details below. We'll have it open in Gmail, ready to send — no copy-pasting.