verify-tests-fail-without-fix

Automate MAUI UI test verification in CI workflows using PowerShell and Git.

23.3k|2.0k|Updated May 8, 2020
One-click install
npx skills add https://github.com/dotnet/maui --skill verify-tests-fail-without-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-tests-fail-without-fix
Source: https://github.com/dotnet/maui/tree/main/.github/skills/verify-tests-fail-without-fix
Command: npx skills add https://github.com/dotnet/maui --skill verify-tests-fail-without-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the verification of UI tests to ensure regressions are detected when a fix is not present and that tests pass after applying a fix. It integrates with Git and CI workflows to validate changes in MAUI projects and reduces manual testing effort.

Core Features & Use Cases

  • Verify Failure Mode: Runs UI tests to confirm they fail when no fix is present.
  • Full Verification Mode: Validates both tests and fixes when a fix is included.
  • CI Integration: Works with pull requests and CI workflows to auto-detect changed tests and report results.

Quick Start

Run in CI or locally to validate UI tests. pwsh .github/skills/verify-tests-fail-without-fix/scripts/verify-tests-fail.ps1 -Platform android pwsh .github/skills/verify-tests-fail-without-fix/scripts/verify-tests-fail.ps1 -Platform ios -TestFilter "Issue33356" -RequireFullVerification

Frequently Asked Questions about verify-tests-fail-without-fix

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

FAQPage Schema
How do I automate UI test failure checks for MAUI projects in CI workflows?

Automate UI test failure checks for MAUI projects by running PowerShell scripts that verify tests fail without a fix and pass after applying it. This skill integrates with CI workflows and pull requests to auto-detect changed tests and generate verification reports.

What is verify failure mode for UI tests and when is it needed?

Verify failure mode for UI tests runs tests to confirm they fail when no fix is present, ensuring regressions are detected. It is needed when validating changes in MAUI projects to reduce manual testing effort and ensure fixes address the actual issues.

Do I need PowerShell and Git to run UI test verification scripts?

Yes, you need PowerShell, Git, and the .NET SDK to execute UI test verification scripts. These tools manage diffs, run tests across platforms like Android and iOS, and generate verification reports within CI workflows or local environments.

Can I filter UI tests by platform and test name during verification?

Yes, you can filter UI tests by platform and test name during verification using command-line parameters. Specify the platform with `-Platform` and target specific tests with `-TestFilter` to narrow the verification scope for MAUI projects.

What's the best way to validate that UI test fixes work across multiple platforms?

The best way to validate UI test fixes across multiple platforms is to use full verification mode, which runs tests across platforms like Android and iOS to confirm they pass after applying a fix. This ensures fixes are effective and regressions are caught.

Why does full verification mode require a fix to be included?

Full verification mode requires a fix to be included because it validates both tests and fixes together, ensuring tests pass after the fix is applied. Without the fix, it cannot confirm that the changes resolve the detected regressions in MAUI projects.