You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, there is integrated way to automatically test web resources (such as JavaScript files) that are part of a solution in model-driven Power Apps applications.
While it is straightforward to attach and associate a web resource with a model-driven app, validating its behavior is can be manual and difficult to validate different test cases. This introduces risks of regressions and makes it difficult to guarantee the quality of custom client-side logic.
Describe the solution you'd like
Introduce a new testing function:
Preview.AssertJavaScript({WebResource: string, Location: string, Setup: string, Run: string, Expected: string})
Functionality:
Allow users to specify the name of a JavaScript web resource or local location of the JS file
Define setup scripts
Define the script/function to run
Define JavaScript to run and the expected outcome.
The test engine should be able to:
Query and retrieve the definition of the specified JavaScript web resource.
Reference a local JS file included with Native Source control integration as part of a solution
Execute unit tests for the resource in an isolated sandbox environment, preventing side effects.
Compare the actual outcome with the expected outcome and report results.
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem? Please describe.
Currently, there is integrated way to automatically test web resources (such as JavaScript files) that are part of a solution in model-driven Power Apps applications.
While it is straightforward to attach and associate a web resource with a model-driven app, validating its behavior is can be manual and difficult to validate different test cases. This introduces risks of regressions and makes it difficult to guarantee the quality of custom client-side logic.
Describe the solution you'd like
Introduce a new testing function:
Preview.AssertJavaScript({WebResource: string, Location: string, Setup: string, Run: string, Expected: string})
Functionality:
The test engine should be able to:
Example Usage:
Where mockXrm.js could be included with the yaml test
Benefits:
Additional Notes:
Describe alternatives you've considered
No response
Additional context?
No response
The text was updated successfully, but these errors were encountered: