تشغيل أي مهارة في Manus بنقرة واحدة

browser-testing

النجوم٤

التفرعات٠

آخر تحديث١٦ مايو ٢٠٢٦ في ١٣:١٣

Automated browser testing, interaction automation, and form testing. Use when the user needs to test web pages, automate browser interactions, fill forms, test validation, run multi-step wizards, or test login/signup flows.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

ironbee-ai

ironbee-ai/ironbee-devtools-skills

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

محللو ضمان جودة البرمجيات والمختبرونمهن الحاسوب والرياضيات·SOC 15-1253

SKILL.md

readonly

المزيد من هذا المستودع

نفس المستودع

ironbee-android-devtools-cli

ironbee-ai/ironbee-devtools-skills

CLI for driving an Android emulator (AVD) over adb. Use when the user needs to connect to an emulator (attach to a running one or boot/manage an AVD), tap/swipe/type on the UI, read the UI/accessibility tree, take screenshots or screen recordings, capture logcat, capture HTTP(S) requests in-process (Frida OkHttp hook — no proxy/CA, pinning bypassed), mock/intercept HTTP responses, pin a W3C trace id across app API calls, measure app performance, wait for network idle, or compare a screen against a Figma design. Emulator-only (no physical devices, no on-device tracepoints); network capture/mocking needs a rootable emulator image. Requires daemon; connect a device before other commands. Also covers the creds-gated Jira and Linear issue-tracker domains: fetch/search issues, download attachments, attach evidence, comment, transition/set state, and report verification results back to the tracker.

2026-07-164

ironbee-backend-devtools-cli

ironbee-ai/ironbee-devtools-skills

CLI for backend service verification — drive HTTP/1.1+HTTP/2, gRPC, GraphQL, and WebSocket endpoints; capture logs from file, Docker, and Kubernetes sources; and verify state against Postgres, MySQL, or SQLite databases with snapshot/diff and change-feed primitives. Use when the user needs to call backend APIs over any of those protocols, assert on log lines or database rows, replay captured curl/HAR requests, manage session-scoped cookies/default headers, or correlate flows with W3C trace ids. Also covers the creds-gated Jira and Linear issue-tracker domains: fetch/search issues, download attachments, attach evidence, comment, transition/set state, and report verification results back to the tracker.

2026-07-164

ironbee-browser-devtools-cli

ironbee-ai/ironbee-devtools-skills

Automates browser interactions using Playwright for web testing, debugging, and automation. Use when the user needs to navigate websites, take screenshots, fill forms, click elements, extract page content (HTML/text), audit accessibility (ARIA/AX tree), measure Web Vitals performance, monitor console logs and HTTP requests, mock API responses, execute JavaScript in browser, inspect React components, compare UI with Figma designs, manage reusable scenarios, or perform non-blocking debugging with tracepoints, logpoints, and exception monitoring. Also covers the creds-gated Jira and Linear issue-tracker domains: fetch/search issues, download attachments, attach evidence, comment, transition/set state, and report verification results back to the tracker.

2026-07-164

ironbee-node-devtools-cli

ironbee-ai/ironbee-devtools-skills

CLI for debugging Node.js backend processes with non-blocking inspection. Use when the user needs to connect to Node.js processes (by PID, name, Docker, or port), set tracepoints/logpoints/exceptionpoints, capture call stacks and local variables, inspect console logs, capture the process's outbound HTTP requests (egress) with W3C trace-context injection, or run reusable scenarios. Requires daemon; connect before other debug commands. Also covers the creds-gated Jira and Linear issue-tracker domains: fetch/search issues, download attachments, attach evidence, comment, transition/set state, and report verification results back to the tracker.

2026-07-164

ironbee-python-devtools-cli

ironbee-ai/ironbee-devtools-skills

CLI for debugging running Python processes with non-blocking inspection via debugpy (Debug Adapter Protocol). Use when the user needs to attach to a Python process (already-listening debugpy, PID injection, process name, or Docker), set tracepoints/logpoints/exceptionpoints, capture call stacks and local variables, dump all thread stacks (deadlock/GIL diagnosis), read stdout/stderr logs, capture the process's outbound HTTP requests (egress) with W3C trace-context injection, or run reusable scenarios. Requires daemon and `debugpy` installed in the target's Python environment; connect before other debug commands. Also covers the creds-gated Jira and Linear issue-tracker domains: fetch/search issues, download attachments, attach evidence, comment, transition/set state, and report verification results back to the tracker.

2026-07-164

ironbee-terminal-devtools-cli

ironbee-ai/ironbee-devtools-skills

CLI for driving interactive terminal programs (shells, REPLs, full-screen TUIs) over a pseudo-terminal (PTY). Use when the user needs to spawn a CLI/REPL/TUI attached to a TTY, type commands and keystrokes (tmux key syntax), wait for expected output before sending more input, capture raw scrollback or the rendered screen grid, send process signals, resize the terminal, or run a one-shot command and read its output + exit code. The platform spawns the process itself (it does not attach to a pre-existing external process). For server APIs use the backend CLI; for Node.js process debugging use the node CLI. Also covers the creds-gated Jira and Linear issue-tracker domains: fetch/search issues, download attachments, attach evidence, comment, transition/set state, and report verification results back to the tracker.

2026-07-164

name	browser-testing
description	Automated browser testing, interaction automation, and form testing. Use when the user needs to test web pages, automate browser interactions, fill forms, test validation, run multi-step wizards, or test login/signup flows.
allowed-tools	Bash(ironbee-browser-devtools-cli:*)

Browser Testing Skill

Automated browser testing, interaction automation, and form testing using Browser DevTools CLI.

When to Use

This skill activates when:

User asks to test a web page or application
User wants to automate browser interactions
User needs to verify UI behavior
User wants to automate form submission
User needs to test form validation
User mentions multi-step forms or wizards
User wants to test login/signup flows

Capabilities

Navigation

ironbee-browser-devtools-cli navigation go-to --url "https://example.com"
ironbee-browser-devtools-cli navigation go-back-or-forward --direction back
ironbee-browser-devtools-cli navigation go-back-or-forward --direction forward
ironbee-browser-devtools-cli navigation reload

Interaction

All accept CSS selector or ref (e1, @e1) from ARIA snapshot.

ironbee-browser-devtools-cli interaction click --selector "#button"
ironbee-browser-devtools-cli interaction click --selector "e1"   # ref from a11y take-aria-snapshot
ironbee-browser-devtools-cli interaction fill --selector "#input" --value "text"
ironbee-browser-devtools-cli interaction select --selector "#dropdown" --value "option"
ironbee-browser-devtools-cli interaction hover --selector "#element"
ironbee-browser-devtools-cli interaction press-key --key "Enter"
ironbee-browser-devtools-cli interaction scroll --mode bottom
ironbee-browser-devtools-cli interaction drag --source-selector "#drag" --target-selector "#drop"

Content Capture

ironbee-browser-devtools-cli content take-screenshot --name "screenshot"
ironbee-browser-devtools-cli content get-as-html
ironbee-browser-devtools-cli content get-as-text
ironbee-browser-devtools-cli content save-as-pdf --name "page"

Synchronization

ironbee-browser-devtools-cli sync wait-for-network-idle

Mocking & Stubbing

ironbee-browser-devtools-cli stub mock-http-response --pattern "**/api/**" --response '{"status":200}'
ironbee-browser-devtools-cli stub intercept-http-request --pattern "**/api/**" --modifications '{"headers":{}}'
ironbee-browser-devtools-cli stub list
ironbee-browser-devtools-cli stub clear

Basic Testing Workflow

Navigate: Go to the page under test
Wait: Ensure page is fully loaded
Snapshot (optional): a11y take-aria-snapshot to get refs (e1, e2) for stable element targeting
Interact: Click, fill, scroll (use --selector "e1" for refs or CSS selector)
Verify: Check page state, take screenshots
Document: Report results

Form Automation Patterns

Basic Form Fill

# Fill text input
ironbee-browser-devtools-cli interaction fill \
  --selector "#email" \
  --value "test@example.com"

# Fill password
ironbee-browser-devtools-cli interaction fill \
  --selector "#password" \
  --value "SecurePass123"

# Click submit
ironbee-browser-devtools-cli interaction click \
  --selector "button[type=submit]"

Select Dropdown

ironbee-browser-devtools-cli interaction select \
  --selector "#country" \
  --value "US"

Checkbox/Radio

# Check checkbox
ironbee-browser-devtools-cli interaction click \
  --selector "#terms-checkbox"

# Select radio option
ironbee-browser-devtools-cli interaction click \
  --selector "input[name=plan][value=premium]"

Multi-Step Wizard

SESSION="--session-id wizard-test"

# Step 1: Personal Info
ironbee-browser-devtools-cli $SESSION interaction fill --selector "#name" --value "John Doe"
ironbee-browser-devtools-cli $SESSION interaction fill --selector "#email" --value "john@example.com"
ironbee-browser-devtools-cli $SESSION interaction click --selector "#next-step"

# Wait for step 2
ironbee-browser-devtools-cli $SESSION sync wait-for-network-idle

# Step 2: Address
ironbee-browser-devtools-cli $SESSION interaction fill --selector "#address" --value "123 Main St"
ironbee-browser-devtools-cli $SESSION interaction select --selector "#state" --value "CA"
ironbee-browser-devtools-cli $SESSION interaction click --selector "#next-step"

# Step 3: Confirm
ironbee-browser-devtools-cli $SESSION sync wait-for-network-idle
ironbee-browser-devtools-cli $SESSION interaction click --selector "#submit"

Validation Testing

Test Required Fields

# Submit empty form
ironbee-browser-devtools-cli interaction click --selector "button[type=submit]"

# Check for error messages
ironbee-browser-devtools-cli content get-as-text --selector ".error-message"

Test Invalid Input

# Invalid email
ironbee-browser-devtools-cli interaction fill --selector "#email" --value "not-an-email"
ironbee-browser-devtools-cli interaction click --selector "button[type=submit]"

# Check validation error
ironbee-browser-devtools-cli content get-as-html --selector ".email-error"

Session-Based Testing

SESSION="--session-id my-test"

# Navigate
ironbee-browser-devtools-cli $SESSION navigation go-to --url "https://example.com"

# Interact
ironbee-browser-devtools-cli $SESSION interaction click --selector ".login-btn"
ironbee-browser-devtools-cli $SESSION interaction fill --selector "#email" --value "test@example.com"

# Verify
ironbee-browser-devtools-cli $SESSION content take-screenshot --name "after-login"

# Cleanup
ironbee-browser-devtools-cli session delete my-test

Best Practices

Use sessions for multi-step flows
Wait for network idle after navigation and actions
Take screenshots after important actions for verification
Use specific selectors to avoid wrong elements
Test empty submission first for validation testing
Clear fields before filling (use interaction fill which clears first)
Handle dynamic fields with wait strategies
Screenshot after errors for documentation
Batch steps when useful: For long flows, run execute --code "..." with callTool() reduces round-trips (see ironbee-browser-devtools-cli execute reference).