skills.rest
trancee
tranceeCOMMUNITY
Explore all skills by this author →
GitHub

understanding-the-testing-pyramid

Guide Android test suite sizing using small, medium, and big scope frameworks.

Updated Jul 20, 2026
Search Tags:#android-testing#ci-optimization#testing-pyramid#instrumented-tests#test-scope#robolectric
One-click install
npx skills add https://github.com/trancee/MeshLink-template --skill understanding-the-testing-pyramid-trancee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: understanding-the-testing-pyramid
Source: https://github.com/trancee/MeshLink-template/tree/main/.agents/skills/android-testing-skills/fundamentals/concepts/understanding-the-testing-pyramid
Command: npx skills add https://github.com/trancee/MeshLink-template --skill understanding-the-testing-pyramid-trancee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves common confusion regarding Android test sizing, helping teams avoid slow CI pipelines and high flake rates caused by over-reliance on heavy instrumented tests.

Core Features & Use Cases

  • Test Sizing Guidance: Provides the correct 3-layer framing (small, medium, big) for Android testing.
  • Strategic Alignment: Clarifies the distinction between test scope and execution location (local vs. instrumented).
  • Use Case: Use this skill when your team is debating whether to write a new test as a unit test or an Espresso test, or when you need to explain why your CI suite is taking too long to run.

Quick Start

Ask the assistant to evaluate your current test suite distribution and suggest how to rebalance it according to the small, medium, and big scope framework.

Frequently Asked Questions about understanding-the-testing-pyramid

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

FAQPage Schema
How do I optimize Android test suites to reduce slow CI pipeline execution?▼

Rebalance Android test suites using the small, medium, and big scope framework to reduce heavy instrumented tests, optimizing CI execution speed and lowering flake rates.

What is the correct framework for sizing Android tests to maintain a balanced testing pyramid?▼

The correct Android test sizing framework uses three layers: small, medium, and big scope, distinguishing test scope from execution location to maintain a balanced testing pyramid.

How do I decide whether to write a new Android test as a unit test or an Espresso instrumented test?▼

Evaluate test scope independently from execution location using the small, medium, and big scope framework to choose between local Robolectric unit tests and instrumented Espresso tests.

Does Robolectric execution location affect test scope classification in Android CI optimization?▼

Robolectric execution location does not dictate test scope. Android CI optimization clarifies test scope separately from local or instrumented execution location within the small, medium, and big framework.

What are the limitations of blending conflicting test framings when designing Android test strategy?▼

Blending conflicting test framings causes misattributed numeric ratios and scope misclassification, leading to over-reliance on heavy instrumented tests, increased CI execution time, and higher flake rates.

Related Skills

Explore More Software Engineering Skills→
tranceetrancee

running-tests-on-gradle-managed-devices

Automate instrumented Android test provisioning and execution on Gradle Managed Devices.

Community
Advanced
skydovesskydoves
303

understanding-the-testing-pyramid

Explain Android small/medium/big test scopes and 70/20/10 ratio attribution.

Community
Basic
fornewidfornewid
5

https://developer.android.com/agents/skills/testing/testing-setup/skill

Audit Android project dependencies and configure testing frameworks.

Community
Advanced
xu-xiangxu-xiang
1.8k

tdd-workflow

Enforce test-driven development workflows with 80% coverage across unit, integration, and E2E tests.

Community
Basic