creating-test-structure
Creating Test Structure
Build the test skeleton first, then implementation.
This skill converts a markdown test plan into test scaffolding by either:
- creating a new spec file, or
- inserting new suites/tests/hooks into an existing spec file.
It produces:
- real
describe/it/ hook blocks - readable test names
- pseudo-code comments for every setup, action, and assertion
When to Use
- You have a test plan and need a fast, consistent scaffold.
- You need to append new test sections to an existing spec.
- You want to separate structure decisions from implementation details.
- You want a handoff file for
writing-webdriverio-code.
More from klamping/webdriverio-skills
writing-webdriverio-code
Use when implementing, extending, or fixing WebdriverIO tests, including converting pseudo-code scaffolds into clean WDIO commands, selectors, waits, and assertions.
21analyze-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.
13gathering-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