klamping/webdriverio-skills

running-webdriverio-tests

Run WebdriverIO test files from the command line.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/klamping/webdriverio-skills --skill running-webdriverio-tests

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

Running WebdriverIO Tests

Main Command

bash
npx wdio

Config is in wdio.conf.js by default.

Project Context Files

Before selecting run commands, read project cache files when available:

  • .webdriverio-skills/project-context.md
  • .webdriverio-skills/project-context.json
  • .webdriverio-skills/custom-rules.md
  • references/website-analysis/<target>/website-analysis.md

Use 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.

Duration

Tests take 20 seconds to 5 minutes. Do not treat a slow test as a failure.

Selecting Tests to Run

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.

By spec file

bash
# Single file
npx wdio --spec=test/specs/home.js

# Multiple files
npx wdio --spec=test/specs/home.js --spec=test/specs/register.js

By suite

Suite names are defined in the WebdriverIO config file under the suites property.

bash
npx wdio --suite=auth

Excluding files

bash
npx wdio --exclude=test/specs/home.js

Can be mixed with --spec or --suite.

Key CLI Options

OptionDescription
--specRun specific spec file(s) or wildcard
--suiteRun a named suite from wdio.conf.js
--excludeExclude spec file(s) from run
--logLeveltrace, debug, info, warn, error, silent
--bailStop after N failures (default: 0 = run all)
--maxInstancesNumber of parallel browser instances (2–10)
--baseUrlOverride base URL for browser.url() calls
--repeatRepeat specs/suites N times

Log Level

  • Use --logLevel=trace when debugging (maximum output)
  • Use default (info) when confirming tests pass (less noise)
bash
npx wdio --logLevel=trace --spec=test/specs/home.js

Bail

bash
npx wdio --bail=1

Max Instances

bash
npx wdio --maxInstances=3

Base URL

Changes the base server used with relative paths (e.g., browser.url('./homepage.html')).

bash
npx wdio --baseUrl=https://example.com/

Isolating Individual Tests (Mocha)

Edit the test file temporarily to add .only or .skip.

Run only specific tests

js
describe.only("Form Fields", function () { ... });
it.only("should submit form", function () { ... });

Mocha docs: exclusive tests

Skip specific tests

js
it.skip("should return -1 unless present", function () { ... });

Mocha docs: inclusive tests

Remember to revert `.only`/`.skip` changes after debugging.

Verwandte Aufgaben