Build and CI investigation
Measure the existing workflow, inspect the slow stages and make changes against a repeatable baseline. Keep the checks that catch real problems.
Android Test Automation & Gradle Build Optimisation
Spend less time waiting for confidence in a release.
Slow builds and unreliable tests make even small changes expensive. I help Android teams find where feedback is getting stuck and improve the checks they use to ship.
Where I can help
For teams with long Gradle or CI runs, fragile UI tests, or too much repetitive manual release testing.
Useful test coverage
Choose checks around important behaviour and past failures. Improve unit, integration or UI testing where it gives the team actionable feedback.
Test infrastructure
Investigate flaky tests, improve their setup and make failures easier to diagnose. Document the workflow so the team can maintain it.
A manageable first step
Bring a representative build, a recent pipeline run and the tests that cause the most trouble. We can agree a focused investigation, establish a baseline and choose the first improvement to implement and verify.
From the project catalogueClient work Freelance & full-time roles Client work
Relevant work
blackned
Android platform engineering with faster build and delivery workflows.
Android / AOSP · Security · CI/CD
lexoffice
Strengthening Android UI testing and its infrastructure.
Android · UI testing · Automation
GLS
Testing and delivery support for logistics and field operations.
Android · Test automation · Logistics
Before we start
Can you guarantee a percentage improvement?
No. The opportunity depends on your project and its constraints. The blackned case study below reports results from that engagement; it is not a forecast for another codebase.
Do we need more UI tests?
Not necessarily. The aim is useful feedback. Some behaviours are better checked below the UI, while key user journeys may justify end-to-end coverage.
Can you work with our existing CI?
We start by looking at your current pipeline, infrastructure and access constraints. The scope can focus on the parts you can change without replacing the whole setup.
Tell me where you need help.
Tell me where the team is losing time: local builds, CI, unreliable tests or manual release checks. Existing timings are helpful if you have them.