writing-webdriverio-code
Writing WebdriverIO Code
Convert scaffold comments into production-ready test code.
This skill can take either:
- a scaffold created by
creating-test-structure, or - an existing WebdriverIO spec that needs new tests, refactors, or bug fixes.
In both cases, it produces concrete WebdriverIO implementation that is stable, readable, and debuggable.
When to Use
- A scaffold exists and needs conversion from pseudo-code to WDIO commands/assertions.
- An existing test file needs additional scenarios.
- Existing tests are flaky, brittle, or incorrect and need fixes.
When Not to Use
More from klamping/webdriverio-skills
analyze-website
Use when investigating and documenting website structure, components, functionality importance, and version-to-version differences for human understanding and test planning.
14running-webdriverio-tests
Run WebdriverIO test files from the command line. Use when debugging tests, gathering context about test behavior, or verifying changes resolved an issue.
13creating-test-structure
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.
10gathering-context
Use when investigating a failing WebdriverIO test and you need to understand what the test was doing and where it broke.
10skipped-test-manager
Use when temporarily skipping failing WebdriverIO tests for app bugs or unimplemented functionality, while tracking ownership, ticket linkage, and re-enable status.
9managing-project-customizations
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.
9