testing Skill
Test patterns, fixture structure, and when to use E2E vs unit tests. Published by microsoft in webui.
Decision snapshot
Is this a fit?
Testing, Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is testing Skill?
Test patterns, fixture structure, and when to use E2E vs unit tests. Published by microsoft in webui. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Writing
- Testing use cases
- Writing use cases
Declared skill metadata
- Source file: .github/skills/testing/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use testing Skill
- Use it for testing.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/webui
- Skill file: .github/skills/testing/SKILL.md
What it does
Test patterns, fixture structure, and when to use E2E vs unit tests.
Skill instructions
Testing Use this skill when writing or modifying tests in this repository. Rust crate tests Unit tests live alongside code in [cfg(test)] modules. Integration tests go in each crate's tests/ directory. bash cargo test -p microsoft-webui-handler one crate cargo test --workspace all crates cargo xtask test via xtask (part of quality gate) Every code change ships with tests: | Change type | Requirement | |-------------|-------------| | New public API | At least one unit test per function/method | | Bug fix | Regression test that fails without the fix | | Performance change | Benchmark comparison (before/after) | | Refactor | Existing tests pass unchanged | Never remove, weaken, or [ignore] an existing test unless explicitly asked. Shared test utilities (webui-test-utils) The webui-test-utils crate provides common Rust test helpers, builders, and fixtures. Check it before writing new helpers - avoid duplicating across crates. toml [dev-dependencies] webui-test-utils = { path = "../webui-te
Verified compatibility and discovery
Frequently asked questions
What is testing?
testing is a open-source AI agent skill with Copy skill directory. Test patterns, fixture structure, and when to use E2E vs unit tests.
Who is testing best for?
testing is best for reusing agent instructions, scripts, and references, testing workflows, writing workflows.
How do I install testing?
Install or run testing using Copy skill directory. Check testing for the latest setup command.
Is testing actively maintained?
testing may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
