webchat-html-tests Skill
Run Bot Framework Web Chat HTML tests in Docker/Selenium Grid. Use when: running tests/html2, debugging failing HTML tests, updating snapshots, checking grid health, or cleaning leaked Selenium sessions. Published by microsoft in BotFramework-WebChat.
Decision snapshot
Is this a fit?
Browser automation, Testing, Deployment, Includes SKILL.md
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 webchat-html-tests Skill?
Run Bot Framework Web Chat HTML tests in Docker/Selenium Grid. Use when: running tests/html2, debugging failing HTML tests, updating snapshots, checking grid health, or cleaning leaked Selenium sessions. Published by microsoft in BotFramework-WebChat. 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
- Browser automation
- Testing
- Deployment
- Browser automation use cases
- Testing use cases
Declared skill metadata
- Source file: .github/skills/webchat-html-tests/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 webchat-html-tests Skill
- Use it for browser automation.
- Use it for testing.
- Use it for deployment.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/BotFramework-WebChat
- Skill file: .github/skills/webchat-html-tests/SKILL.md
What it does
Run Bot Framework Web Chat HTML tests in Docker/Selenium Grid. Use when: running tests/html2, debugging failing HTML tests, updating snapshots, checking grid health, or cleaning leaked Selenium sessions.
Skill instructions
Web Chat HTML Tests Run the HTML test harness, keep Selenium Grid healthy, and debug failures without keeping all of the operational detail in the skill body. When to Use - Running tests/html2 for a branch or PR - Debugging a failing HTML or snapshot test - Updating snapshots after an intentional visual change - Checking whether Selenium Grid is ready or leaking sessions Procedure 1. Start Selenium Grid Use the bundled script instead of pasting long Docker commands. For a focused test run, keep the default scale of 2 Chrome nodes: sh ./.github/skills/webchat-html-tests/scripts/start-grid.sh For a full run, match Jest's 4 workers: sh CHROMESCALE=4 ./.github/skills/webchat-html-tests/scripts/start-grid.sh 2. Wait for Grid Readiness sh python3 ./.github/skills/webchat-html-tests/scripts/wait-for-grid.py Stop if the script times out or if the node summary does not show ready nodes. 3. Run Tests Run the full suite: sh ./.github/skills/webchat-html-tests/scripts/run-html-tests.sh Run a focus
Verified compatibility and discovery
Frequently asked questions
What is webchat-html-tests?
webchat-html-tests is a open-source AI agent skill with Copy skill directory. Run Bot Framework Web Chat HTML tests in Docker/Selenium Grid. Use when: running tests/html2, debugging failing HTML tests, updating snapshots, checking grid health, or cleaning leaked Selenium.
Who is webchat-html-tests best for?
webchat-html-tests is best for reusing agent instructions, scripts, and references, browser automation workflows, testing workflows, deployment workflows.
How do I install webchat-html-tests?
Install or run webchat-html-tests using Copy skill directory. Check webchat-html-tests for the latest setup command.
Is webchat-html-tests actively maintained?
webchat-html-tests 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.
