skipped-test-manager
Skipped Test Manager
Manage temporary test skips as controlled technical debt.
This skill standardizes how tests are skipped, documented, tracked, reported, and re-enabled.
When to Use
- A test fails due to confirmed app-level bug.
- A test targets not-yet-implemented product functionality.
- A skip already exists and needs tracking, reporting, or re-enable review.
When Not to Use
- The issue is a test bug that should be fixed directly.
- The failure can be resolved with a small, safe test update.
- You cannot provide reason/ownership metadata for the skip.
Project Context Files
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.
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.
10managing-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