test-full

Run complete Android test suites and generate coverage reports.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill test-full
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-full
Source: https://github.com/oscardlfr/AndroidCommonDoc/tree/main/skills/test-full
Command: npx skills add https://github.com/oscardlfr/AndroidCommonDoc --skill test-full

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ANDROID_COMMON_DOC, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for a complete test suite with a detailed coverage report, enabling thorough verification and validation of Android application code.

Core Features & Use Cases

  • Sequential Testing: Runs all tests in a sequential order, ensuring a full suite execution.
  • Full Coverage Report: Generates comprehensive coverage reports for each module.
  • Filtering Options: Offers various parameters to include shared modules, filter specific modules, and run benchmarks.

Quick Start

Run the test suite with the command '/test-full'.

Frequently Asked Questions about test-full

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

FAQPage Schema
How do I run a complete Android test suite with coverage analysis?

You can run a complete Android test suite with coverage analysis by executing the '/test-full' command. This triggers sequential test execution and generates a comprehensive coverage report for each module to identify untested code areas.

What is sequential testing and how does it help verify Android app code?

Sequential testing runs all tests in a specific order to ensure full suite execution. This approach provides thorough verification and validation of Android application code by systematically executing every test case without interference.

Do I need AndroidCommonDoc setup to generate full coverage reports for Android apps?

Yes, you need a project with the AndroidCommonDoc setup and a configured project root directory. This prerequisite environment is required to execute the complete test suite and generate detailed coverage reports for each module.

Can I filter specific modules or include shared modules when running Android tests?

Yes, you can filter specific modules, include shared modules, and run benchmarks. The test suite offers various parameters to customize execution, ensuring the coverage report targets the exact modules you need to verify.

What's the best way to identify untested code areas in an Android application?

The best way to identify untested code areas is to generate a full coverage report using a complete test suite. Running '/test-full' executes all tests sequentially and produces comprehensive coverage data for each module to pinpoint gaps.

Why does my Android test suite require a configured project root directory?

Your Android test suite requires a configured project root directory to properly locate and execute tests across all modules. This setup ensures the sequential testing process can accurately generate comprehensive coverage reports for the entire application.