extracting-test-artifacts

Extract test artifacts from Android devices using ADB pull and push operations.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/trancee/MeshLink-template --skill extracting-test-artifacts-trancee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extracting-test-artifacts
Source: https://github.com/trancee/MeshLink-template/tree/main/.agents/skills/android-testing-skills/adb/transfer/extracting-test-artifacts
Command: npx skills add https://github.com/trancee/MeshLink-template --skill extracting-test-artifacts-trancee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves common permission and binary corruption issues encountered when pulling test artifacts like screenshots, databases, and logs from Android devices during CI/CD or local development.

Core Features & Use Cases

  • Binary-Safe Extraction: Uses exec-out and tar to prevent PTY-related byte corruption when pulling binary files or directories.
  • Permission Handling: Provides standardized patterns for using run-as on debuggable builds and leveraging TestStorage for modern AndroidX testing.
  • Performance Optimization: Implements modern ADB flags like brotli compression and sync-based pushing to accelerate large data transfers.

Quick Start

Use the extracting-test-artifacts skill to pull the database file from the debuggable package com.example.app using the binary-clean exec-out method.

Frequently Asked Questions about extracting-test-artifacts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pull test artifacts from an Android device without binary corruption?

To pull test artifacts without binary corruption, use ADB exec-out combined with tar. This method prevents PTY-related byte corruption that typically occurs when transferring binary files or directories from Android devices.

How do I extract a database file from a debuggable Android app using ADB?

Extract a database from a debuggable Android app by utilizing the ADB run-as command. This pattern handles permission constraints on debuggable builds, allowing you to access and pull files from the app's private data directory.

What is the best way to collect Android test artifacts in a CI/CD pipeline?

The best way to collect Android test artifacts in CI/CD is through automated ADB pull operations. Leveraging modern AndroidX TestStorage and platform-tools flags ensures reliable, automated artifact collection across various storage partitions.

Does ADB support run-as for accessing private app data on non-debuggable builds?

ADB run-as is specifically designed for debuggable builds to bypass permission constraints. For non-debuggable builds, you must rely on modern AndroidX TestStorage patterns to manage test artifact collection across storage partitions.

How can I speed up large ADB pull operations for test artifacts?

Speed up large ADB pull operations by implementing modern ADB flags like brotli compression and sync-based pushing. These performance optimizations accelerate large data transfers significantly during test artifact extraction.

Why are my pulled binary test files corrupted when using ADB?

Pulled binary test files become corrupted due to PTY-related byte interference during standard ADB transfers. Using the binary-safe exec-out method with tar prevents this corruption and maintains binary integrity.