القائمة
Run WebdriverIO test files from the command line. Use when debugging tests, gathering context about test behavior, or verifying changes resolved an issue.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when investigating and documenting website structure, components, functionality importance, and version-to-version differences for human understanding and test planning.
Use when creating or extending WebdriverIO test structure from a markdown test plan by adding describe/it/hooks and pseudo-code comments without implementing WDIO commands yet.
Use when investigating a failing WebdriverIO test and you need to understand what the test was doing and where it broke.
Use when diagnosing and coordinating fixes for failing WebdriverIO tests across context gathering, test runs, and implementation skills, while limiting retry loops and avoiding rabbit holes.
Use when initializing or refreshing project-specific WebdriverIO context so other skills can reuse cached configuration, conventions, and environment details with lower token and execution cost.
Use when temporarily skipping failing WebdriverIO tests for app bugs or unimplemented functionality, while tracking ownership, ticket linkage, and re-enable status.
| name | running-webdriverio-tests |
| description | Run WebdriverIO test files from the command line. Use when debugging tests, gathering context about test behavior, or verifying changes resolved an issue. |
npx wdio
Config is in wdio.conf.js by default.
Before selecting run commands, read project cache files when available:
.webdriverio-skills/project-context.md.webdriverio-skills/project-context.json.webdriverio-skills/custom-rules.mdreferences/website-analysis/<target>/website-analysis.mdUse these files to prefer project-approved scripts, configs, environment flags, and server targets.
Use website analysis references to prioritize high-impact route/component test runs first.
Resolve <target> as lowercase site host (prefer explicit URL or project baseUrl host), fallback unknown-target.
If files are missing or stale, run managing-project-customizations first.
Tests take 20 seconds to 5 minutes. Do not treat a slow test as a failure.
Prefer package.json scripts discovered in project context when they exist (e.g. npm run test:e2e, npm run test:wdio:debug) before using raw npx wdio.
# Single file
npx wdio --spec=test/specs/home.js
# Multiple files
npx wdio --spec=test/specs/home.js --spec=test/specs/register.js
Suite names are defined in the WebdriverIO config file under the suites property.
npx wdio --suite=auth
npx wdio --exclude=test/specs/home.js
Can be mixed with --spec or --suite.
| Option | Description |
|---|---|
--spec | Run specific spec file(s) or wildcard |
--suite | Run a named suite from wdio.conf.js |
--exclude | Exclude spec file(s) from run |
--logLevel | trace, debug, info, warn, error, silent |
--bail | Stop after N failures (default: 0 = run all) |
--maxInstances | Number of parallel browser instances (2–10) |
--baseUrl | Override base URL for browser.url() calls |
--repeat | Repeat specs/suites N times |
--logLevel=trace when debugging (maximum output)info) when confirming tests pass (less noise)npx wdio --logLevel=trace --spec=test/specs/home.js
npx wdio --bail=1
npx wdio --maxInstances=3
Changes the base server used with relative paths (e.g., browser.url('./homepage.html')).
npx wdio --baseUrl=https://example.com/
Edit the test file temporarily to add .only or .skip.
describe.only("Form Fields", function () { ... });
it.only("should submit form", function () { ... });
it.skip("should return -1 unless present", function () { ... });
Remember to revert .only/.skip changes after debugging.