wox-generate-smoke-test-case

Generates Go UI smoke test cases for Wox features and plugin settings using the automation driver.

27.3k|2.4k|Updated Dec 19, 2013
One-click install
npx skills add https://github.com/Wox-launcher/Wox --skill wox-generate-smoke-test-case
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wox-generate-smoke-test-case
Source: https://github.com/Wox-launcher/Wox/tree/main/.agents/skills/wox-generate-smoke-test-case
Command: npx skills add https://github.com/Wox-launcher/Wox --skill wox-generate-smoke-test-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing meaningful UI smoke tests for the Wox launcher requires deep knowledge of its automation driver, shared-process harness, and plugin settings semantics. This Skill analyzes feature code end to end, recommends the highest-value smoke coverage, and generates focused Go test cases that follow the repository's established conventions.

Core Features & Use Cases

  • Feature Analysis: Traces a Wox feature from UI component through controller, persisted state, and error paths to identify real integration boundaries worth testing.
  • Plugin Settings Matrix: Maps every exposed plugin setting to the behavior it changes and recommends which settings deserve smoke coverage versus unit tests.
  • Test Generation: Produces numbered Go smoke test files under wox.core/test/smoke with proper build constraints, doc comments, semantic waits, and cross-platform command handling.
  • Use Case: A developer adding a new Calculator plugin setting asks for smoke coverage; the Skill inspects the setting's runtime consumers, recommends a flow proving the setting changes query results, and generates a passing test case verified with make smoke.

Quick Start

Use the wox-generate-smoke-test-case skill to analyze this Wox feature, recommend valuable smoke flows, and generate the selected case.

Frequently Asked Questions about wox-generate-smoke-test-case

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a UI smoke test for a Wox feature?

Trace the feature from UI entry point through controller and persisted state, then generate a Go test under wox.core/test/smoke using the automationdriver client. Drive the UI with semantic actions and client.WaitFor, and verify with make smoke followed by the case selector.

How do I test Wox plugin settings with smoke tests?

Map each setting in SettingDefinitions to the runtime behavior it changes, then build a flow that alters the setting and asserts the real user-visible effect. Place plugin cases under wox.core/test/smoke/launcher/plugin/<plugin>/ with the next unused three-digit number.

When should Wox behavior get a smoke test instead of a unit test?

Reserve smoke tests for real-process boundaries: native UI, lifecycle, persistence, plugin integration, platform, accessibility, or rendering. Pure local logic and branches already covered at the same boundary belong in unit tests.

Does Wox smoke testing work on Windows, macOS, and Linux?

Yes, but commands executed by a case are interpreter- and platform-dependent. Use syntax shared across targeted interpreters or select commands with runtime.GOOS, normalize path separators, and skip intentionally platform-specific behavior explicitly.

Why does a Wox smoke test fail on query result waits?

Query and result state is generation-bound, so setting the same query value may be a no-op and refreshes replace dynamic result IDs. Force a real query transition, wait for launcher.results=complete, and re-resolve dynamic IDs after each refresh.