一键在 Manus 中运行任何 Skill

archestra-dev-e2e

星标3,908

分支1,070

更新时间2026年6月5日 09:29

Use when writing, debugging, or running Archestra Playwright e2e tests, API/UI fixtures, WireMock-backed tests, local/CI e2e setup, or test selectors.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

archestra-ai

archestra-ai/archestra

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Archestra E2E Testing

Use this skill for files under platform/e2e-tests/ and for frontend/backend changes that require Playwright coverage.

Run commands from platform/ unless specifically instructed otherwise.

Commands

pnpm test:e2e
tilt trigger e2e-test-dependencies

tilt trigger e2e-test-dependencies starts WireMock and seeds test data to the database.

In development, e2e tests use the development database. Local data can make e2e tests fail locally.

Check WireMock health at http://localhost:9092/__admin/health.

WireMock environment variables

Use port 9092 for the Tilt e2e dependency setup:

ARCHESTRA_OPENAI_BASE_URL=http://localhost:9092/v1
ARCHESTRA_ANTHROPIC_BASE_URL=http://localhost:9092
ARCHESTRA_GEMINI_BASE_URL=http://localhost:9092

Use port 9091 for the alternate local WireMock setup:

ARCHESTRA_OPENAI_BASE_URL=http://localhost:9091/v1
ARCHESTRA_ANTHROPIC_BASE_URL=http://localhost:9091
ARCHESTRA_GEMINI_BASE_URL=http://localhost:9091

Local and CI setup

Local e2e uses docker-compose setup through Tiltfile.test.
CI uses a kind cluster and Helm deployment.
CI kind config is .github/kind.yaml.
CI Helm values are .github/values-ci.yaml.
CI NodePort services use frontend 3000, backend 9000, and metrics 9050.
CI e2e checks include drizzle-kit check, codegen, and database migrations.

Fixtures

Use the Playwright fixtures pattern.
Import from ./fixtures in API/UI test directories.
API fixtures include makeApiRequest, createAgent, deleteAgent, createApiKey, deleteApiKey, createToolInvocationPolicy, deleteToolInvocationPolicy, createTrustedDataPolicy, and deleteTrustedDataPolicy.
UI fixtures include goToPage and makeRandomString.

Example:

import { test } from "./fixtures";

test("API example", async ({ request, createAgent, deleteAgent }) => {
  const response = await createAgent(request, "Test Agent");
  const agent = await response.json();
  // test logic...
  await deleteAgent(request, agent.id);
});

Locator best practices

Prefer Playwright's recommended locators over raw locator() calls. In priority order:

page.getByRole() - accessible elements by ARIA role, such as buttons, links, and headings.
page.getByText() - text content.
page.getByLabel() - form controls by label.
page.getByPlaceholder() - input elements by placeholder.
page.getByTestId() - custom test IDs using E2eTestId constants from @archestra/shared.

Avoid raw CSS selectors, XPath selectors, and arbitrary timeouts. Use Playwright auto-waiting instead.

// good
await page.getByRole("button", { name: /Submit/i }).click();
await page.getByLabel(/Email/i).fill("test@example.com");
await page.getByTestId(E2eTestId.CreateAgentButton).click();

// avoid
await page.locator(".submit-btn").click();
await page.locator("#email-input").fill("test@example.com");
await page.waitForTimeout(1000); // use auto-waiting instead

Reference: https://playwright.dev/docs/locators#quick-guide

同仓库更多 Skills

同仓库

migrate-to-archestra

archestra-ai/archestra

Migrate an existing agentic PoC/pilot (Claude Code project files, MCP configs, hooks, local tools, openclaw config, or similar hand-rolled setup artifacts) into an Archestra instance. Use when the user wants to move, port, or convert an existing agentic setup into an Archestra pilot.

2026-06-303.9k

archestra-dev-frontend

archestra-ai/archestra

Use when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.

2026-06-293.9k

access-request-intake

archestra-ai/archestra

Collect a complete system-access request from the user and file it via the IT service desk. Use when someone asks to request, grant, or set up system/application access for an employee.

2026-06-263.9k

archestra-dev-bench-analysis

archestra-ai/archestra

Map-reduce a finished archestra-bench run into a Tier-1/Tier-2 improvement report using Claude subagents (same analysis as the Rust analyzer, no API key).

2026-06-223.9k

archestra-dev-rust-napi

archestra-ai/archestra

Use when editing Rust in this repo — the NAPI crates under platform/archestra-rs (Node bindings, generated TypeScript bindings, telemetry, validation/errors) or the standalone archestra-bench Rust workspace (core/runner/cli/analyzer) — including Rust build/test checks.

2026-06-193.9k

cipher-decoder

archestra-ai/archestra

Decode an encoded message using the bundled cipher scripts. Use when handed a hex-encoded or otherwise scrambled blob and asked for its plaintext; run the scripts rather than reasoning about the bytes by hand.

2026-06-193.9k

name	archestra-dev-e2e
description	Use when writing, debugging, or running Archestra Playwright e2e tests, API/UI fixtures, WireMock-backed tests, local/CI e2e setup, or test selectors.

Archestra E2E Testing

Use this skill for files under platform/e2e-tests/ and for frontend/backend changes that require Playwright coverage.

Run commands from platform/ unless specifically instructed otherwise.

Commands

pnpm test:e2e
tilt trigger e2e-test-dependencies

tilt trigger e2e-test-dependencies starts WireMock and seeds test data to the database.

In development, e2e tests use the development database. Local data can make e2e tests fail locally.

Check WireMock health at http://localhost:9092/__admin/health.

WireMock environment variables

Use port 9092 for the Tilt e2e dependency setup:

ARCHESTRA_OPENAI_BASE_URL=http://localhost:9092/v1
ARCHESTRA_ANTHROPIC_BASE_URL=http://localhost:9092
ARCHESTRA_GEMINI_BASE_URL=http://localhost:9092

Use port 9091 for the alternate local WireMock setup:

ARCHESTRA_OPENAI_BASE_URL=http://localhost:9091/v1
ARCHESTRA_ANTHROPIC_BASE_URL=http://localhost:9091
ARCHESTRA_GEMINI_BASE_URL=http://localhost:9091

Local and CI setup

Local e2e uses docker-compose setup through Tiltfile.test.
CI uses a kind cluster and Helm deployment.
CI kind config is .github/kind.yaml.
CI Helm values are .github/values-ci.yaml.
CI NodePort services use frontend 3000, backend 9000, and metrics 9050.
CI e2e checks include drizzle-kit check, codegen, and database migrations.

Fixtures

Use the Playwright fixtures pattern.
Import from ./fixtures in API/UI test directories.
API fixtures include makeApiRequest, createAgent, deleteAgent, createApiKey, deleteApiKey, createToolInvocationPolicy, deleteToolInvocationPolicy, createTrustedDataPolicy, and deleteTrustedDataPolicy.
UI fixtures include goToPage and makeRandomString.

Example:

import { test } from "./fixtures";

test("API example", async ({ request, createAgent, deleteAgent }) => {
  const response = await createAgent(request, "Test Agent");
  const agent = await response.json();
  // test logic...
  await deleteAgent(request, agent.id);
});

Locator best practices

Prefer Playwright's recommended locators over raw locator() calls. In priority order:

page.getByRole() - accessible elements by ARIA role, such as buttons, links, and headings.
page.getByText() - text content.
page.getByLabel() - form controls by label.
page.getByPlaceholder() - input elements by placeholder.
page.getByTestId() - custom test IDs using E2eTestId constants from @archestra/shared.

Avoid raw CSS selectors, XPath selectors, and arbitrary timeouts. Use Playwright auto-waiting instead.

// good
await page.getByRole("button", { name: /Submit/i }).click();
await page.getByLabel(/Email/i).fill("test@example.com");
await page.getByTestId(E2eTestId.CreateAgentButton).click();

// avoid
await page.locator(".submit-btn").click();
await page.locator("#email-input").fill("test@example.com");
await page.waitForTimeout(1000); // use auto-waiting instead

Reference: https://playwright.dev/docs/locators#quick-guide