test-suite-verification

Runs the TpIDS test suite via run-tests.ps1 and reports TRX-backed results before handoff.

Updated Aug 24, 2026
One-click install
npx skills add https://github.com/aggutierrez98/TP-TD --skill test-suite-verification-aggutierrez98
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-suite-verification
Source: https://github.com/aggutierrez98/TP-TD/tree/main/.agents/skills/test-suite-verification
Command: npx skills add https://github.com/aggutierrez98/TP-TD --skill test-suite-verification-aggutierrez98

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Closing a feature, bugfix, or refactor without running the full test gate risks shipping regressions, and ad-hoc test runs often produce unverifiable or incomplete results. This Skill enforces a consistent end-of-task verification workflow for the TpIDS project so every handoff is backed by explicit, real test outcomes. ## Core Features & Use Cases - Mandatory test gate: Runs tests\tools\run-tests.ps1 -IncludeIntegration (unit + integration) and requires exit code 0 before responding to the user. - UI suite protocol: The FlaUI desktop UI suite (-IncludeUi) only runs after warning the user that it locks the desktop for about 5 minutes and receiving explicit confirmation. - UiFilter discipline: -UiFilter is never applied by the agent's own decision; it requires an explicit user request plus a warning about missed cross-flow regressions. - Honest reporting: Reports the exact command, exit code, and real test counters read from output or TestResults/*.trx, and lists any suites left unrun with the reason. - Use Case: After finishing a bugfix in the BLL layer, the agent runs the default gate, verifies the TpIDS.sln build separately, and reports actual TRX counters instead of assuming green. ## Quick Start Use the test-suite-verification skill to run the full test gate and report the real results before closing this task.

Frequently Asked Questions about test-suite-verification

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

FAQPage Schema
How do I run the TpIDS test suite before finishing a task?▼

Run powershell -NoProfile -ExecutionPolicy Bypass -File tests\tools\run-tests.ps1 -IncludeIntegration, which executes unit and integration tests. Exit code 0 means green; any failure must be fixed and rerun before handoff.

How do I run the FlaUI UI test suite safely?▼

The UI suite takes control of the desktop for about 5 minutes and needs an unlocked session and local SQL Server. Warn the user first, wait for explicit confirmation, then run the runner with -IncludeIntegration -IncludeUi.

When should I use -UiFilter to run only some UI tests?▼

Only when the user explicitly requests it for speed, never by the agent's own choice. Warn that a filtered run misses cross-flow regressions, and if the filter matches no tests the runner fails with exit 1 by design.

What environment is required for the integration and UI tests?▼

The runner needs MSBuild (VS 2022+), VSTest, and NuGet or a local package cache. Integration and UI additionally require local SQL Server (default .\SQLEXPRESS, configurable via -SqlServer) and sqlcmd on PATH.

What if SQL Server is not available for integration tests?▼

Run the runner without flags to execute only the unit tests, which need no database. Explicitly report that integration and UI suites could not run and why, rather than claiming success.

Why does the test runner fail when a filter matches zero tests?▼

The runner includes a guard that fails any suite executing 0 tests, such as a -UiFilter typo, instead of reporting an empty green. It also validates TRX files requiring at least 1 executed test and 0 failures per suite.