wox-test-ensurance

Runs Wox core, Go UI unit, and native smoke test suites and fixes failures until they pass.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running the full Wox test workflow requires coordinating three separate suites (core integration, headless Go UI unit tests, and native smoke tests), cleaning up stale Wox processes, and triaging failures without breaking real product behavior. This Skill automates that entire loop from the repository root.

Core Features & Use Cases

  • Full Suite Orchestration: Executes make test, make test-go-ui-unit, and make smoke in sequence from the Wox repository root, including headless Linux support via xvfb-run.
  • Preflight Process Cleanup: Detects and force-stops stale Wox binaries, debug processes, and VS Code-launched runtimes that could hold ports or interfere with smoke tests.
  • Root-Cause Failure Triage: Investigates failures by checking recent implementation changes first, fixing production code for real regressions, and only modifying tests when they are stale or invalid.
  • Use Case: After modifying Wox launcher code, invoke the skill to run all three test suites, automatically diagnose a failing retained-widget test, fix the underlying async ordering bug, and rerun everything until green.

Quick Start

Use the wox-test-ensurance skill to run the Wox test suites and fix any failures until they all pass.

Frequently Asked Questions about wox-test-ensurance

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

FAQPage Schema
How do I run all Wox tests from the repository root?

Run make test for the core integration suite, make test-go-ui-unit for headless Go UI tests, and make smoke for the native single-process UI. This skill runs all three in order and fixes failures until they pass.

How do I run Wox smoke tests on headless Linux?

Set GO_UI_SMOKE_RUNNER to "xvfb-run -a" before running make smoke. This provides a virtual display so the native Go UI smoke tests can execute without a physical screen.

Why do Wox smoke tests fail when another Wox instance is running?

Stale Wox or debug processes can hold ports or keep old state alive, conflicting with the smoke test's own Wox process. The skill's preflight step force-stops matching Wox binaries and debug processes before running the suites.

When should a failing Wox test be changed instead of the code?

Change a test only when evidence shows the product behavior is correct and the test is stale, over-specified, or testing the wrong layer. Real regressions exposed by tests should be fixed in production code first.

Can I run just one Wox test command instead of the full suite?

Yes. If you request one exact command such as make test, only that command runs and its failures are fixed. The full three-suite workflow only executes when the skill is explicitly invoked for test assurance.