Open Grant-Archibald-MS opened 1 week ago
Some possible examples within the Experimental namespace to trial the experience and determine fit before consideration for the wider TestEngine namespace.
Experimental.SimulateDataverse({
Action: "Patch",
Entity: "Processes",
When: {Status: 1}),
Then: {} // Return value
});
Experimental.SimulateDataverse({
Action: "Query",
Entity: "Workflow",
When: Table({Status: "Active", CreatedOn: "> 2023-01-01"}),
Then: Table({Name: "Test", Owner: "John Doe"}) // Return Value
});
Experimental.SimulateWorkflow({
Name: "SetupWizard>GetTenantID",
Then: {Id:"a1234567-1111-2222-3333-4444555666"}
});
Experimental.SimulateConnector({
Name: "Office365Groups",
When: {Action: "ListOwnedGroupsV2"},
Then: Table({Name: "Test"})
});
Is your feature request related to a problem? Please describe.
When I need to ensure that data in Connectors or Dataverse are in a specific state for testing purposes.
This process can be time-consuming and often leads to non-deterministic tests due to the dynamic nature of the data.
It would be beneficial to have a way to simulate Dataverse queries conditionally, allowing for deterministic tests without needing to set the Dataverse state manually.
For connectors it would be beneficial to have a way simulate connector actions so that the behavior of the application can be tested for expected and edge case scenarios.
For example, when testing the CoE Kit Setup and Install Wizard there are stages that start a Power Automate Cloud flow. The application then waits for Dataverse to be in a defined state and then continues with the install process.
Describe the solution you'd like
I would like to have a feature in the different Power Apps cases (Canvas, Model Driven Custom Pages - Entity List and Details) that allows for queries made to Dataverse to be conditionally simulated. When these queries occur, they should be replaced with example data. Key aspects of this feature should include:
This feature would enable deterministic tests by allowing developers to simulate specific data states without manually setting the Dataverse state. It would also save time and improve the reliability of tests.
Describe alternatives you've considered
No response
Additional context?
No response