[QUESTION] Unable to run Test Engine - Invalid File Path: TestPlanDefinition in test config file
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp, playwright
- Domain
- cli, testing-qa
Research direction
Start with src\PowerAppsTestEngine\config.dev.json and samples\basicgallery\TestPlan.fx.yaml, then reproduce the command from bin\Debug\PowerAppsTestEngine using the paths shown. Trace where the test configuration reports the invalid TestPlanDefinition path; done means the basic gallery test plan runs without that error.
Written by the indexing model from the issue text.
Description
Does this question already exist in our backlog?
- I have checked and confirm this is a new question.
What is your question?
I am unable to run the basic gallery test plan. Here are my repo steps.
- Clone repository
cd PowerApps-TestEngine\srcdotnet build- Installed the browsers for Playwright via
playwright.ps1 install - Uploaded the solution to my environment.
- Created and configured a config.dev.json file in the src\PowerApsTestEngine folder as such:
{
"environmentId": "valid environment",
"tenantId": "valid tenant",
"testPlanFile": "../../samples/basicgallery/testPlan.fx.yaml",
"outputDirectory": "",
"user1Email": "my email"
}
- Removed logical name from TestPlan.fx.yaml within the basicgallery folder and replaced it with
appId: valid app GUID - Ran the following command in bin\Debug\PowerAppsTestEngine
`dotnet PowerAppsTestEngine.dll -i ......\samples\basicgallery\TestPlan.fx.yaml -e [valid environment] -t [valid tenant]
In the command line, I see 'Invalid file path'. In the debug log I see 'Invalid file path: TestPlanDefinition in test config file.'
What component are you experiencing the issue with?
Other
What pac version are you using?
1.40
- 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