Testing & QA
3,371 results
- Modernization Integration TestsMicrosoftOfficialRun multi-layer integration tests for modernized Java applications. Supports 4 layers - Layer 1 (TestContainers), Layer 2 (Smoke Tests), Layer 3 (Azure Integration), Layer 4 (Behavioral Comparison). Java projects only - skip if source code is not Java.
- Project DecompositionMicrosoftOfficialSingle-source codebase decomposition: scans a project scope, builds the module dependency graph, counts LOC by language, computes skip patterns (caller-supplied ∪ .gitignore ∪ baseline), and (when grouping is required) produces topology groupings with L3 quality validation. One skill owns ProjectProfile JSON, grouping protocols, and quality gates.
- Quality GatesMicrosoftOfficialRuns quality gate validation at each workflow stage. Supports 4 gate types: spec-quality, spec-to-plan, plan-to-tasks, completeness. Produces gate pass/fail reports with actionable feedback. Triggers: "run quality gate", "validate spec quality", "spec quality", "plan coverage", "check plan coverage", "validate plan to tasks", "check task traceability", "verify task completeness", "run…
- Runtime ValidationMicrosoftOfficialRuntime validation for migrated applications — covers testing strategy (planning phase) and test execution (validation phase): startup verification, integration testing, and end-to-end flow validation. Use when: (1) designing test strategy during planning phase (teamlead reads Part 1) (2) verifying a migrated app starts and runs correctly (3) writing or executing integration / E2E tests (tester…
- Verify Test BaselineMicrosoftOfficialGenerate and run post-migration tests from the frozen baseline specification.
- Handoff Brief GeneratorMicrosoftOfficialCreates comprehensive handoff documentation for sales reps going on vacation or transitioning deals. Generates structured briefs with deal status, activities, next steps, contacts, and risks. Use when user says "I'm going on vacation", "create handoff brief", "coverage brief for my deals", "vacation handoff", "out of office brief", "transition my deals", or "backup documentation".
- Transformers To MlxHugging FaceOfficialConvert Hugging Face transformers language models to MLX format for Apple Silicon inference. Use when asked to convert a model from transformers to MLX, port a model to MLX, create an MLX implementation of a model, or test/validate an MLX model conversion.
- Test LocalMicrosoftOfficialRuns an Agent 365 AI Teammate agent locally and opens AgentsPlayground for interactive local testing. Works with any AI Teammate stack — .NET (AgentFramework, Semantic Kernel), Node.js (LangChain, OpenAI, Claude SDK, Semantic Kernel, Google ADK), or Python (AgentFramework, LangChain, OpenAI, Claude, Semantic Kernel, Google ADK).
- Testing BlocksAdobeOfficialGuide for testing code changes in AEM Edge Delivery projects including blocks, scripts, and styles. Use this skill after making code changes and before opening a pull request to validate functionality. Covers unit testing for utilities and logic, browser testing with Playwright/Puppeteer, linting, performance validation, and guidance on which tests to maintain vs use as throwaway validation.
- Generating Upgrade Test BaselineMicrosoftOfficialGenerates behavior-locking tests before a .NET upgrade using the external dotnet-test plugin. Use when executing a generate-test-baseline task for projects with upgrade compatibility risks.
- Jsts Framework MigrationMicrosoftOfficialMigrate a JavaScript or TypeScript project from one framework to another while preserving behavior, integrations, build workflows, and validation. Covers application-framework migrations (for example Gatsby to Astro, Create React App to Vite) and tooling/test-framework migrations (for example Karma/Jasmine to Vitest).
- Managing Dotnet Test InstallationMicrosoftOfficialInstalls the external dotnet-test plugin when its test-generation agent is unavailable. Use when a user selects AI test generation during an upgrade but code-testing-generator is not loaded.
- Managing Winforms MvvmMicrosoftOfficialImplements MVVM pattern in WinForms applications (.NET 8+) with ViewModels, Commands, and DataContext. Use when user explicitly requests MVVM implementation, setting up ViewModel with INotifyPropertyChanged or ObservableObject, implementing ICommand or RelayCommand, wiring Form.DataContext, binding controls to ViewModel properties, creating Commands for button clicks, or separating business…
- Reviewing Execution IntegrityMicrosoftOfficial.NET evidence for an integrity review — how invented, substituted, drifted, or silenced work shows up in a .NET diff. Contributes the .NET signatures an integrity reviewer checks against: an unverified package version, a hand-written stand-in for a NuGet package, changes outside the task's scope, or a warning/test/exception suppressed instead of fixed.
- Triaging Powershell Analyzer FindingsMicrosoftOfficialDecide whether a PSScriptAnalyzer PSUseCompatibleCommands / PSUseCompatibleTypes finding is a real PowerShell 5.1 → 7.x break or one of four measured false-positive classes: a function defined elsewhere in the estate, an abbreviated parameter prefix such as '-fore', a symbol the compatibility profile dropped during generation, or a provider dynamic parameter such as 'Set-ItemProperty -Type'.
- Typescript Runtime ValidationMicrosoftOfficialValidate a JavaScript or TypeScript project by authoring and replaying an eval plan that can build or type-check, run tests, start the project, probe endpoints, and exercise browser flows. Use this directly or when another Modernizer skill delegates its required validation.
- Netlify DatabaseNetlifyOfficialZero-config Postgres for Netlify apps via @netlify/database — querying data from Functions/Edge Functions, writing schema migrations, setting up Drizzle ORM, local dev with netlify dev, database branches for deploy previews, and migrating an existing Postgres project onto Netlify.
- Netlify Edge FunctionsNetlifyOfficialWrite, route, cache, and debug Netlify Edge Functions, the Deno-based TypeScript or JavaScript handlers in netlify/edge-functions that run at the network edge in front of static files and serverless functions.
- Netlify FunctionsNetlifyOfficialWrite, configure, and deploy Netlify serverless functions in TypeScript, JavaScript, or Go. Use this when adding an API endpoint or backend route, adding a contact form handler, wiring auth or Identity signup/login hooks, identifying which Netlify user is calling a private or team-login-protected app, building streaming or AI-proxy responses, scheduling cron jobs, running long background jobs…
- WiqdMicrosoftOfficialOrchestrator for building, testing, deploying, and managing Microsoft 365 Copilot declarative agents via the wiqd CLI. Triggers: open devui, debug agent, test agent visually, watch agent run, ask in devui, agent debugger, evaluate, test, run evals, check agent, generate evals, analyze results, compare runs, submit feedback, report a bug, request a feature, suggest an improvement, list my…
- Chatgpt App SubmissionOpenAIOfficialUse when a developer needs a ChatGPT Apps submission import file from an MCP server. Inspect the implementation, generate chatgpt-app-submission.json with app info, tool-hint justifications, positive and negative test cases, then report review findings and outputSchema warnings.
- Openai Platform API KeyOpenAIOfficialUse when Claude Code is asked to build, run, test, debug, or configure an OpenAI-backed or provider-unspecified AI app, UI, script, CLI, generator, or tool, especially requests phrased only as "using AI" or generators driven by forms/user input; also use for OPENAI_API_KEY or sk-proj setup.
- Slack AgentVercelOfficialUse when building Slack agents/bots with eve (Vercel's filesystem-first agent framework), @vercel/connect, or eve/channels/slack. Covers defineAgent/defineTool patterns, Vercel Connect credential brokering, Slack channel setup, testing requirements, and quality standards.
- Azuresql Db CIMicrosoftOfficialRuns integration tests against the Azure SQL Database container (Private Preview, local engine) in CI. Use when setting up GitHub Actions, Azure Pipelines, or GitLab CI to test against Azure SQL DB; when adding a database service container to a CI workflow; when tests need a real Azure SQL engine in the pipeline; or when you see "service container", "health-cmd", "ACR_USERNAME/ACR_PASSWORD"…