test-local

Validates CloudStub module publishing, auto-downloading, and runtime loading via simulated consumer workflows.

2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/cloudstub/cloudstub --skill test-local-cloudstub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-local
Source: https://github.com/cloudstub/cloudstub/tree/main/.claude/skills/test-local
Command: npx skills add https://github.com/cloudstub/cloudstub --skill test-local-cloudstub

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires java, python3, gradle, and includes scripts (resource) components.

What problem does it solve?

This skill solves the challenge of verifying that a newly developed CloudStub service module correctly integrates with the standalone distribution path, ensuring it can be published, auto-downloaded, and loaded by the server just as a real user would experience.

Core Features & Use Cases

  • End-to-End Validation: Automates the entire pipeline from publishing to mavenLocal to auto-downloading and loading the module in a clean environment.
  • Checksum Verification: Automatically generates required checksums for local artifacts to satisfy the downloader's security requirements.
  • Use Case: Use this skill when you have finished implementing a new service module and need to confirm that the provisioning, dependency resolution, and runtime loading work perfectly before merging your code.

Quick Start

Run the test-local skill for the dynamodb service to verify its full distribution and loading path.

Frequently Asked Questions about test-local

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

FAQPage Schema
How do I validate a JVM-based AWS mock service module end-to-end before merging?

To validate a JVM-based AWS mock service module end-to-end, you can automate the pipeline from publishing to mavenLocal to auto-downloading and runtime loading. This simulates a real consumer installation to verify provisioning and dependency resolution.

What is the full distribution and loading lifecycle for CloudStub service modules?

The full distribution and loading lifecycle for CloudStub service modules involves publishing artifacts to mavenLocal, HTTP-based auto-downloading, and runtime plugin loading. This sequence mirrors a real-world consumer installation for JVM-based AWS mock services.

Do I need Java and Gradle to test the local distribution of CloudStub modules?

Yes, you need Java 17+, Python 3, and a properly configured Gradle build environment to execute the full integration test pipeline for validating CloudStub service modules and their runtime loading sequence.

How do I generate checksums for local Maven artifacts to satisfy the auto-downloader?

To generate checksums for local Maven artifacts during module validation, the testing pipeline automatically creates the required checksums. This satisfies the downloader's security requirements before runtime plugin loading occurs.

Why does my CloudStub module fail to load during the local integration test?

Your CloudStub module may fail to load during the local integration test if the publish-to-mavenLocal, checksum verification, or HTTP-based auto-download sequence is improperly configured, or if the Gradle build environment lacks the correct Java 17+ setup.

Can I use this integration test for non-JVM AWS mock services?

No, this integration test targets JVM-based AWS mock services specifically. It validates the runtime plugin loading sequence and dependency resolution within a Gradle build environment designed for Java-based service modules.