ADB Kit for QA Testers: Better Android Bug Reports from the Browser
“Can’t reproduce.” Every QA tester has seen those two words on a ticket they were sure was solid. The bug was real. You saw it. But the report had a blurry phone photo of the screen, three lines of steps and no logs, because getting logs meant asking a developer to set up ADB on your machine.
ADB Kit closes that gap. It puts the everyday ADB tools into a browser tab: mirror and control the device, take screenshots, record the screen, install APKs and stream logcat. No platform-tools, no terminal, no IT ticket to install an SDK. This post shows how a manual or exploratory tester can use it to file bug reports developers can actually act on.
Why QA teams like a browser-based ADB
- Zero setup on locked-down laptops. Many testers cannot install developer tools. ADB Kit runs in Chrome or Edge over WebUSB, so a browser is enough.
- Local-first. Device data is not sent to a server. Pre-release builds, test accounts and internal screens stay on your machine.
- Free. All current features are free; a paid plan for automation is planned for later.
If you are completely new to it, read how to use ADB in your browser with WebUSB first.
One-time setup (5 minutes)
- On the test device, enable Developer options and turn on USB debugging.
- Plug the device into your computer and open adbkit.com/app in Chrome or Edge.
- Click connect, choose the device in the browser prompt, and accept the debugging prompt on the phone.
Firefox and Safari cannot connect over USB, so keep a Chromium browser for testing days. For devices on a test rack across the room, set up ADB over Wi-Fi instead.
The tester’s loop with ADB Kit
1. Install the build under test
Drop the APK from your CI or build share into ADB Kit. You confirm before it installs, so there are no surprise installs on the wrong device. Our guide on installing an APK from your browser covers the details. Installing straight from the browser also avoids the “which build is on this phone?” confusion that comes from sideloading through chat apps and download folders.
2. Test on the big screen
Mirror the device’s live screen in the browser and control it with your mouse: tap, swipe and rotate. For exploratory sessions, this is far more comfortable than hunching over a phone, and it means your screen-share in a triage call shows the device directly.
3. Start logcat before you start the repro
Open live logcat and leave it running. Use filtering and search to cut through the noise: search for your app’s package name, a tag the developers use, or keywords like “Exception” or “FATAL” right after the bug appears. Seeing an exception at the exact moment of a crash is often the single most useful thing a developer can get from QA.
4. Record the repro
Start a screen recording, reset the app to a clean state, and walk through the steps. ADB Kit records to WebM. A short video showing the steps and the failure is worth a paragraph of written description, and it captures timing problems, such as a button that only breaks when tapped twice quickly, that text cannot.
5. Capture the key frames
Take screenshots of the important states: before, the moment of failure, and the error message if there is one. Screenshots are kept in a session history, so you can grab them during the run and pick the best ones when you write the ticket instead of interrupting your flow.
6. Move files on and off the device
Need to push a test image for an upload test, or pull a file the app exported? ADB Kit transfers files through the device’s Downloads folder.
A bug report template that pairs with ADB Kit
Paste this into your tracker and fill it as you go:
Title: [Screen] What breaks, when
Build: version / build number installed via ADB Kit
Device: model, Android version
Preconditions: account type, app state, network
Steps:
1.
2.
3.
Expected:
Actual:
Attachments:
- Repro video (WebM)
- Screenshots: before / failure / error
- Logcat excerpt: lines around the failure, filtered by package or tag
Frequency: always / intermittent (x of y tries)The attachments section is where ADB Kit does its work. A ticket with a video, screenshots and the relevant log lines rarely comes back as “can’t reproduce.”
Tips from real testing days
- Clear the log noise first. Filter logcat to your app before starting, so the relevant lines are not buried.
- Record short. Start recording just before the key steps. Short clips are easier to review and attach.
- One device, one tab. When testing on several phones, keep each device in its own browser tab or window and name your files with the device model.
- Rotate during the run. Orientation changes are a classic source of crashes, and rotating from the browser makes them easy to include in exploratory passes.
- Keep the cheat sheet handy. Our ADB cheat sheet for screenshots, screen recording and logcat maps each task to its ADB command, useful when you talk to developers who think in commands.
Testing on the go
ADB Kit is also available as a mobile app on Google Play and the App Store, with live screen, logcat, APK install, file transfer and Wireless ADB over Wi-Fi. That is handy for field testing, device labs without a spare laptop, or quickly checking logs on a colleague’s test phone.
How ADB Kit compares
If your team already uses heavier tools, ADB Kit is not a replacement for a full IDE. It is the quick, no-install option for the tasks testers do every day. For a broader view, see Android Studio alternatives for quick ADB tasks.
Wrapping up
Good bug reports are not about writing more. They are about attaching the right evidence: the build, the video, the screenshots and the log lines. ADB Kit puts all four within reach of any tester with a Chromium browser and a USB cable, with nothing to install and nothing leaving your machine. Open the ADB Kit page to get started, or launch the web app at adbkit.com/app.
FAQ
Do QA testers need Android Studio or platform-tools to use ADB Kit?
No. ADB Kit speaks ADB directly from Chrome, Edge or another Chromium-based desktop browser over WebUSB, so there is nothing to install and no terminal to use.
Can I test on a device without a USB cable?
Yes. ADB Kit can connect over Wi-Fi and TCP/IP through a small agent on your own computer, and the ADB Kit mobile apps for Android and iOS support Wireless ADB over Wi-Fi.
Is device data from test phones uploaded anywhere?
No. ADB Kit is local-first and does not send device data to a server, which matters when test devices hold pre-release builds or test accounts.
A local-first workspace for Android in your browser and on your phone: mirror and control a device, capture screenshots and recordings, install APKs, stream logcat and move files over USB or Wi-Fi.