[Feature]: Enhanced Health Metrics
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- testing-qa
Research direction
Start by reviewing issue #594 and the current PowerAppsTestEngine health-check report flow shown in the PowerShell example. Define how solution selection, component discovery, coverage scope, and the HTML summary should work for the listed Power Platform resources. Done means the feature has agreed behavior for identifying covered and uncovered components and generating the requested coverage report.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
While the current implementation Model Drivel Application - Health Check Test Coverage Report #594 provides a pass/fail metric for test execution, it does not offer insight into the coverage of tests across the testable resources within a Power Platform solution. This limits the ability to assess how comprehensively the solution is being validated through automated tests.
Describe the solution you'd like
Introduce a feature that enables users to:
- Specify a solution (e.g., by name or ID)
- Automatically discover testable components within that solution
- Generate a coverage report indicating which components are covered by tests and which are not
- Define scope to indicate what components that the tests health check metric should cover
Testable Components to Include
- Canvas Apps
- Pages (Screens) - Model-Driven Apps
- Entity List Pages
- Entity Detail Pages
- Custom Pages - Web Resources
- JavaScript files used in Model-Driven Apps - Dataverse
- Plugins
- Entities - AI Builder
- Trained AI Models
Describe alternatives you've considered
No response
Additional context?
Current process example using features from Model Drivel Application - Health Check Test Coverage Report #594 a
$env:user1Email = "test@contoso.onmicrosoft.com"
dotnet PowerAppsTestEngine -i test.te.yaml -p mda -e $envId -t $tenantId -d $testPage --run-name "Sample"
dotnet PowerAppsTestEngine -i test2.te.yaml -p mda -e $envId -t $tenantId -d $testPage --run-name "Sample"
$folderPath = "$env:USERPROFILE\AppData\Local\Temp\Microsoft\TestEngine\TestOutput"
$reportPath = [System.IO.Path]::Combine($folderPath, "test_summary_$runName.html")
dotnet PowerAppsTestEngine --run-name "Sample" --output-file $reportPath
Could generate a summary report like
With the health coverage metric of the avaliable tests
- Dominant language
- C#
- Stars
- 150
- Forks
- 55
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/PowerApps-TestEngine
-
new
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
new
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
new
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
question
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in microsoft/PowerApps-TestEngine
Similar issues
-
core dependencies
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
bug frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
NavigationViewItemAutomationPeer implements IInvokeProvider but never advertises the Invoke pattern Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
unoplatform/uno#24629 ·
-
agentic-workflows Needs: Triage :mag: State: In-PR
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Down / Waiting for removal
Difficulty 2/5 1-3 hours Newbie friendliness 70/100