test-engine
Installation
SKILL.md
Skill: Power Apps Test Engine + Playwright
When to Use
Trigger when testing Power Platform apps end-to-end, writing automated test plans, setting up test pipelines, or verifying UI after deployment.
Decision Matrix: Which Testing Approach?
| Approach | When | Language | Selectors | Auth |
|---|---|---|---|---|
| Test Engine (Power Fx YAML) | Standard Canvas/MDA testing, low-code teams | Power Fx in YAML | App-level control names | Built-in Entra handling |
| Raw Playwright (TypeScript) | Complex UI, custom controls, third-party components, visual QA | TypeScript or C# | CSS/XPath DOM selectors | Manual auth scripting |
| Test Engine + Playwright hybrid | Standard tests with occasional DOM access | Power Fx + Preview.PlaywrightAction() | Both | Built-in + direct |
| Manual testing | One-off verification, exploratory testing | N/A | N/A | N/A |
Rule of thumb: Start with Test Engine Power Fx for standard apps. Drop to raw Playwright only when Test Engine abstractions can't reach what you need (custom controls, third-party embedded UIs, visual regression).
AI Accuracy Warning
LLMs are less accurate with Power Fx than mainstream languages (JavaScript, C#, Python) due to smaller training datasets. Always verify Power Fx test steps manually before trusting them in CI/CD. This applies to both test authoring and formula column definitions.