Token导航 LogoToken导航TokenDH.com
开发需要联网github未标认证来源可访问许可证需确认审计提醒

testing-integration测试集成

Agent Skill

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

总安装

388

周安装

16

GitHub Stars

4

下载量

127
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:testing-integration(测试集成)
来源仓库:https://github.com/alphaonedev/openclaw-graph
仓库路径:skills/testing-integration
安装命令:
npx skills add https://github.com/alphaonedev/openclaw-graph --skill testing-integration
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/alphaonedev/openclaw-graph --skill testing-integration

简介

专注于系统集成测试的支持能力。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

  • 适用于微服务、分布式架构下的接口兼容性验证。
  • 可协助编排测试流程、模拟上下游依赖行为。
  • 需明确服务契约与超时设置,防止阻塞主流程。
  • testing-integration 属于开发类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Purpose

This skill facilitates integration testing for APIs and services, focusing on tools like Supertest (Node.js), httpx (Python), Testcontainers for managing test environments, and Pact for contract testing. It ensures end-to-end verification of service interactions, database integrations, and API contracts.

When to Use

Use this skill when verifying API endpoints in a real environment, testing service integrations (e.g., with databases or external services), running containerized tests, or enforcing contracts between microservices. Apply it in CI/CD pipelines for regression testing or when mocking dependencies is insufficient.

Key Capabilities

  • Perform HTTP API testing with Supertest for Node.js apps, including mocking and assertions.
  • Use httpx in Python for asynchronous HTTP requests and integration with databases.
  • Manage test containers via Testcontainers to spin up isolated environments (e.g., Docker-based databases).
  • Conduct contract testing with Pact to define and verify API provider-consumer agreements.
  • Support for service integration testing, such as linking APIs to external services or databases.

Usage Patterns

To use this skill, first install required dependencies (e.g., via npm or pip). Set up test files in your project, configure environments with variables like $API_BASE_URL, and run tests using a test runner. For API tests, structure code to send requests and assert responses. For contract testing, define pacts in separate files and verify them against providers. Always isolate tests with containers to avoid side effects. Example pattern: Import the tool, define a test function, send requests, and handle assertions within 2-3 lines.

Common Commands/API

  • Supertest (Node.js): Use supertest to test Express apps. Command: npm install supertest. Code snippet: const request = require('supertest'); const app = require('./app'); request(app).get('/api/users').expect(200); CLI flag: Run with npx jest --runInBand for sequential tests.
  • httpx (Python): For async HTTP testing. Command: pip install httpx. Code snippet: import httpx response = httpx.get('http://example.com/api/data', headers={'Authorization': f'Bearer {os.environ.get("API_KEY")}'}).json() assert response['status'] == 'success' API endpoint: Pass URLs like https://api.service.com/endpoint with query params (e.g., ?limit=10).
  • Testcontainers: Spin up containers for integration. Command: Add to pom.xml or requirements. Code snippet: GenericContainer container = new GenericContainer("postgres:13").withExposedPorts(5432); container.start(); String jdbcUrl = container.getJdbcUrl(); Config format: Use Docker image specs in YAML, e.g., image: postgres:13 with env vars like $DB_PASSWORD.
  • Pact (Contract Testing): Define and verify contracts. Command: npm install @pact-foundation/pact or pip install pact-python. Code snippet: const {Pact} = require('@pact-foundation/pact'); const pact = new Pact({consumer: 'MyConsumer', provider: 'MyProvider'}); pact.addInteraction({state: 'default', uponReceiving: 'a request'}); API: Use endpoints like /pacts/provider/MyProvider/consumer/MyConsumer/verification for verification, with auth via $PACT_BROKER_TOKEN.

Integration Notes

Integrate this skill by adding it to your build tools: For Node.js, include in Jest or Mocha configs; for Python, use pytest fixtures. Set env vars like $DATABASE_URL for database connections or $SERVICE_API_KEY for authenticated requests. For container integration, ensure Docker is installed and use Testcontainers to link services (e.g., expose ports via withExposedPorts(8080)). When combining with Pact, publish pacts to a broker (e.g., via pact-broker publish --broker-url=$PACT_BROKER_URL). Config format: Use JSON for Pact files, e.g., {"interactions": [...]}, and ensure compatibility with CI tools like GitHub Actions by adding steps like run: docker-compose up -d.

Error Handling

Handle errors by wrapping requests in try-catch blocks. For Supertest, check response status and body: e.g., if .expect(200) fails, log the error with console.error(response.error). In httpx, catch httpx.HTTPError for network issues, e.g.:

try:
    response = httpx.get(url)
    response.raise_for_status()
except httpx.HTTPError as e:
    print(f"Error: {e} - Check $API_BASE_URL")

For Testcontainers, verify container startup with container.isRunning() before tests. In Pact, use pact.verify() and handle mismatches by reviewing pact files. Common patterns: Use env vars for retries (e.g., $RETRY_COUNT=3) and log detailed errors with stack traces.

Concrete Usage Examples

  1. API Integration Test with Supertest: To test a user endpoint in a Node.js app with a database, first set $DB_URL=postgres://user:pass@localhost:5432/db. Write a test file: Import Supertest, send a GET request, and assert the response. Run with npx jest tests/integration.test.js. This verifies the API connects to the database and returns data.
  2. Contract Test with Pact: For a consumer-provider setup, define a pact in a file (e.g., pacts/my-pact.json) with interactions. Use pact.verify() against the provider endpoint (e.g., http://provider.com), passing $PACT_BROKER_TOKEN. Run via npx pact-verifier --provider-base-url=$PROVIDER_URL. This ensures the consumer's expectations match the provider's implementation.

Graph Relationships

  • Related to cluster: "testing" (e.g., shares tags with unit-testing skills).
  • Connected to skills: "api-development" via integration-test tag for API workflows.
  • Links to: "contract-management" through contract-test tag for Pact-based verification.
  • Associated with: "database-integration" due to test containers for database testing.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.68%
按下载量换算44

Claude

26.67%
按下载量换算34

Cursor

20.12%
按下载量换算26

Gemini CLI

9.56%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills