b2c-android-create-mock-data

Generate MockWebServer JSON fixtures from Android service definitions.

Updated Aug 23, 2026

Search Tags:#testing #json #fixtures #android #mock-data #mockwebserver

Ready to run

npx skills add https://github.com/herren-official/product-agents --skill b2c-android-create-mock-data

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: b2c-android-create-mock-data
Source: https://github.com/herren-official/product-agents/tree/main/skills/b2c-Android/create-mock-data
Command: npx skills add https://github.com/herren-official/product-agents --skill b2c-android-create-mock-data

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the generation of MockWebServer JSON fixtures for B2C service tests by analyzing service definitions and producing standardized test resources.

Core Features & Use Cases

Automatically generate JSON fixtures for service endpoints based on discovered metadata.
Enforce consistent file naming and domain/resource mapping to feature module test resources.
Support multiple scenarios (success, apiError, empty, failAuth) to improve test coverage.

Quick Start

Run this skill against your Android project to generate fixtures under feature/{module}/src/test/resources/{domain}/ for each tested endpoint.

Frequently Asked Questions about b2c-android-create-mock-data

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

FAQPage Schema

How do I generate MockWebServer JSON fixtures for Android feature modules?▼

Generating MockWebServer JSON fixtures for Android feature modules is automated by analyzing service definitions and producing standardized test resources under feature/{module}/src/test/resources/{domain}/ with consistent file naming.

Can I create multiple test scenarios like apiError and empty for MockWebServer mock data?▼

Yes, creating multiple test scenarios for MockWebServer mock data is supported, including success, apiError, empty, and failAuth cases, which improves test coverage across different service endpoint responses.

What's the best way to organize mock data fixtures across Android feature modules?▼

Organizing mock data fixtures across Android feature modules is handled by enforcing domain-specific resource mapping, placing generated JSON files into feature/{module}/src/test/resources/{domain}/ directories automatically.

Does generating MockWebServer fixtures require parsing service metadata first?▼

Yes, generating MockWebServer fixtures requires parsing service metadata first, as the skill inspects discovered endpoint definitions and uses local templates to render realistic JSON payloads for your tests.

Why does my Android test mock data have inconsistent naming across endpoints?▼

Inconsistent naming across endpoints happens when test resources are manually created; this skill enforces consistent file naming and domain/resource mapping during JSON fixture generation to eliminate this issue.

Do I need external dependencies to create mock data for B2C service tests?▼

No external dependencies are required to create mock data for B2C service tests; the skill operates using local templates and parsed service metadata to render the JSON fixtures directly.