-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: Access Playwright Actions using Power Fx #337
Comments
Please signoff when this is in the integration branch |
8 tasks
Grant-Archibald-MS
added a commit
that referenced
this issue
Nov 22, 2024
… Fx extensions (#380) * Adding namespace checks and support for Power FX #330 * Adding TestEngine.PlaywrightScript() #335 * Adding TestEngine.PlaywrightAction() #337 * Adding TestEngine.PlaywrightAction docs * Adding TestEngine.PlaywrightScript docs * Update TestEngine.PlaywrightScript.md * Initial portal provider * Partial PowerApps Portal provider implementation * WIP Power Apps Portal provider implementation * Adding TestEngine.GetConnections() * Test update * Adding CreateConnection * Adding TestEngine.CheckConnectionExists * TestEngine.CreateConnection update * Review edits * Add TestEngine.UpdateConnectionReferences() * Solution update * Connection list * Connection and format * Export connections * Package update * NuGet version update * NuGet Updates * Playright updates * Provider update * Review edits. * Update TestEngine namespace * Power Apps Portal update * Format updates * Add default certificate provider * Adding Variables ans Collection support * Remoding date tets * Adding TestEngine.SelectSection() * Adding tests * Format update * Adding MDA module and CoE custom page Sample * Review edit * Adding browser locale change * Adding Experimental.SelectControl() for MDA custom pages * Adding WIP Experimental.SimulateDataverse() * WIP SimuateDataverse GET list * Update for $batch and Query * Basic query use cases * Update .Net 8.0 * Update to .Net 8 * Additional Context error handling * Remove legacy player * Adding SimulateConnector Power Fx function * Updates for Debug/Trace logging * Networking monitoring update * Minior edits * Simulate update * WIP record implementation for SimulateDataverse and SimulateConnector * Sign only Release build record SimulateDataverse and SimulateConnector * Adding Mouse recording * Recorder update and Experimental functions * Review edits * Reviw edits for .Net 8 * Review edits * Adding parameter for custom page * Adding audio recording * Add audio event tracking * Asing storage auth provider * Suppotr for negative test case * Adding error checks for storage state * Adding NotificationTitle error detection * Storage state and permissions example * Update variable state * Refactor to common PowerPlatformLogin * Adding missing common files * Review changes * Adding storage state for #389 * Update samples to storagestate * Adding changes * Log updates and Test Cases * Format update and .Net 8.0 build * Build update * Pull request review edits * Review edit * Review changes * Update dotnet-format.yml * Adding docs
Now merged into branch https://github.com/microsoft/PowerApps-TestEngine/tree/integration This feature has been included in the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
There are times where need to interact with the Playwright page to perform actions on parts of the page. For example, interact with elements inside a component or a PCF control.
Describe the solution you'd like
Provide a module to leverage playwright locator model to apply common actions. For example, consider the following actions
Expose these actions as Power Fx actions that can be included in testSteps. For example, add support scenarios similar to the following:
TestEngine.PlaywrightAction("//button", "click");
TestEngine.PlaywrightAction("//button", "wait");
Describe alternatives you've considered
Could make use of PlaywrightScript() however makers may not have code first skills and would require a Power Fx function to allow interaction with the test page.
Additional context?
No response
The text was updated successfully, but these errors were encountered: