Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Integration Testing

v1.0.1

Automated integration testing with external services using testcontainers, wiremock, localstack. Use when developer needs to set up integration tests for tes...

0· 23·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for ahmed181283/integration-testing.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Integration Testing" (ahmed181283/integration-testing) from ClawHub.
Skill page: https://clawhub.ai/ahmed181283/integration-testing
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install ahmed181283/integration-testing

ClawHub CLI

Package manager switcher

npx clawhub@latest install integration-testing
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
high confidence
Purpose & Capability
The name, description, SKILL.md, templates, and scripts are all consistent with an integration-testing helper for testcontainers, WireMock, LocalStack, and SFTP. The repository provides relevant guides and runnable scripts for those technologies. This dimension is broadly coherent.
!
Instruction Scope
The runtime instructions and included scripts do more than show examples: scripts perform network downloads (curl of a WireMock JAR), call pip to install packages, run Docker commands, start long-lived processes, and append environment configuration to the user's shell profile (~/.bashrc). That expands scope beyond passive examples to persistent system modification and package installation. Notably, setup_testcontainers sets TESTCONTAINERS_RYUK_DISABLED='true' (explicitly disabling automatic cleanup of containers), which contradicts the 'ephemeral' guidance in SKILL.md/SECURITY.md.
Install Mechanism
There is no install spec declared in the registry, but the provided scripts perform installs at runtime: pip installs (testcontainers, localstack, docker packages), curl download of a WireMock JAR from Maven Central, and docker run pulls (e.g., atmoz/sftp). The download sources are known registries (PyPI, Maven Central, Docker Hub), which is expected, but the scripts invoke system-wide installs rather than using isolated virtual environments. This is a medium-risk pattern because it modifies the host and downloads/extracts artifacts.
!
Credentials
The skill declares no required env vars, yet scripts append environment variables into ~/.bashrc (TESTCONTAINERS_HOST_OVERRIDE, TESTCONTAINERS_RYUK_DISABLED, AWS_ACCESS_KEY_ID/SECRET/REGION/ENDPOINT_URL_S3). The AWS values are the typical 'test' placeholders, but writing those and other config to the user's profile is persistent and intrusive. Disabling Ryuk (container cleanup) is disproportionate to a helper script and increases risk of leftover containers and resource exposure.
!
Persistence & Privilege
The scripts intentionally persist configuration by appending to ~/.bashrc and include examples for persistent LocalStack volumes (/tmp/localstack-data). They also include commands and defaults that can leave containers or services running (TESTCONTAINERS_RYUK_DISABLED = 'true', starting LocalStack or WireMock as background/long-running processes). While always:false (no forced inclusion), the skill's actions are persistent on the host if the scripts are executed.
What to consider before installing
This skill appears to do what it says (integration testing), but before running any setup scripts you should: 1) Inspect the scripts line-by-line (they modify ~/.bashrc, run pip install, curl downloads, and docker commands). 2) Do not run them on a production machine — use an isolated VM, disposable developer laptop, or CI runner. 3) Prefer running pip installs inside a virtualenv or container to avoid system-wide changes. 4) Undo or avoid TESTCONTAINERS_RYUK_DISABLED='true' unless you intentionally want containers to persist; enabling it prevents automatic cleanup and may leave running containers and exposed ports. 5) Check the Docker images (e.g., atmoz/sftp) and any external downloads (WireMock jar) you will pull. 6) If you want ephemeral behavior, remove lines that append to ~/.bashrc and avoid persistent LocalStack volume usage. If you are uncomfortable with these persistent changes, treat the repository as reference-only and copy the specific snippets you trust into your own controlled setup.

Like a lobster shell, security has layers — review code before you run it.

awsvk977sdas14atkyyw9w6tx171xh85e4hkcontainersvk977sdas14atkyyw9w6tx171xh85e4hkdevelopmentvk977sdas14atkyyw9w6tx171xh85e4hklatestvk977sdas14atkyyw9w6tx171xh85e4hkmockingvk977sdas14atkyyw9w6tx171xh85e4hksecurityvk977sdas14atkyyw9w6tx171xh85e4hktestingvk977sdas14atkyyw9w6tx171xh85e4hk
23downloads
0stars
2versions
Updated 2h ago
v1.0.1
MIT-0

Integration Testing with External Services

Quick Start

This skill helps you set up integration tests with external services:

  • Testcontainers: Run real services in Docker containers for testing
  • WireMock: Mock HTTP services and APIs
  • LocalStack: Local AWS services (S3) for testing without AWS dependency
  • SFTP: Integration testing with SFTP servers

When to Use This Skill

Use this skill when you need to:

  • Set up integration tests with external services
  • Test applications against real databases/message queues in isolation
  • Mock HTTP APIs for reliable testing
  • Test S3 integration without using real AWS resources
  • Configure automated integration test environments

Setup Options

Testcontainers Setup

For integration tests with real services:

# Basic testcontainers example
from testcontainers.postgres import PostgresContainer

def test_with_postgres():
    with PostgresContainer("postgres:15") as postgres:
        connection_string = postgres.get_connection_url()
        # Run tests with real PostgreSQL

See testcontainers-guide.md for detailed setup.

WireMock Setup

For mocking HTTP services:

# WireMock configuration example
from wiremock import WireMockServer

def test_with_wiremock():
    with WireMockServer() as wiremock:
        wiremock.stub_for(
            request_method="GET",
            request_url="/api/users",
            response_body='{"users": []}'
        )
        # Test against mocked API

See wiremock-patterns.md for common patterns.

LocalStack Setup

For testing S3 without AWS:

# LocalStack S3 testing example
import boto3
from localstack import start_localstack

def test_s3_with_localstack():
    with start_localstack(services=["s3"]) as localstack:
        s3 = boto3.client('s3', endpoint_url=localstack.endpoint_url)
        # Test S3 operations locally

See localstack-s3-config.md for S3 configuration.

SFTP Integration Testing

For testing SFTP connectivity and operations:

# SFTP integration test example
from paramiko import SSHClient

def test_sftp_operations():
    with SSHClient() as ssh:
        ssh.connect('sftp-server', username='test', password='test')
        sftp = ssh.open_sftp()
        # Test SFTP file operations

Available Templates

Ready-to-use test templates for common scenarios:

  • templates/testcontainers-python.py - Python testcontainers setup
  • templates/wiremock-http-tests.py - WireMock HTTP API tests
  • templates/localstack-s33-tests.py - LocalStack S3 integration tests
  • templates/sftp-integration-tests.py - SFTP integration testing

Helper Scripts

Setup scripts to initialize test environments:

  • scripts/setup_testcontainers.py - Configure testcontainers environment
  • scripts/init_wiremock.py - Initialize WireMock server
  • scripts/start_localstack.py - Start LocalStack services

Best Practices

  1. Container Management: Always use context managers for container lifecycle
  2. Port Conflicts: Configure ports to avoid conflicts with local services
  3. Cleanup: Ensure proper cleanup of resources in test teardown
  4. Environment Variables: Use env vars for configuration, avoid hardcoded values
  5. Parallel Testing: Design tests to run in parallel where possible

Getting Help

For detailed setup and patterns, see:

Security & Compliance

This skill is designed SOLELY for legitimate integration testing purposes in isolated development environments.

⚠️ Important Security Notes

  • Development Use Only: Never deploy test containers or services to production networks
  • Isolated Environments: All services run locally and are destroyed after testing
  • Educational Purpose: Designed to teach proper testing methodologies
  • Full Transparency: Source code is fully visible and auditable

For detailed security information, see SECURITY.md

Comments

Loading comments...