[QUESTION] Unable to run Test Engine - Invalid File Path: TestPlanDefinition in test config file

[FragariaChemist]

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.

1. Clone repository
2. cd PowerApps-TestEngine\src
3. dotnet build
4. Installed the browsers for Playwright via playwright.ps1 install
5. Uploaded the solution to my environment.
6. 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"
  }

7. Removed logical name from TestPlan.fx.yaml within the basicgallery folder and replaced it with
   appId: valid app GUID
8. 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

[snamilikonda]

@FragariaChemist currently, there are restrictions on the locations from which input files can be read. Please ensure that the test YAML files are not placed on networked drives, system directories, or user-specific folders such as Desktop or Documents. Any folder located within standard local drives (e.g., C:\ or D:) that is not a restricted system or user-specific path is considered valid. Will track item for message, documentation updates.

[FragariaChemist]

@snamilikonda Yes, moving it directly into a local drive worked. Thank you! I assume it's due to the long path names. What is preferred way to run this - via the RunTests scripts, a dotnet command, or via pac?