[Feature]: MDA Testing Patterns

Start by reviewing the Test Engine scope and the Playwright alternative mentioned in the issue. Map the requested security, monitoring, application interaction, asynchronous process, shift-left, and ALM scenarios before proposing patterns. Done would require documented mini reference examples and guidance covering test creation, execution, deployment, monitoring, and approval workflows.

Is your feature request related to a problem? Please describe.

The current testing framework for Model Driven Applications generally requires browser automation which makes the process of creating automated testing of various components such as Create, Update, and Delete operations, Custom Toolbars, Web Resources with Xrm SDK, and Business Process Flows. This limitation hinders the ability to efficiently test and validate the functionality of applications, leading to potential issues in production.

Additionally, many organizations express the need for a shift-left testing strategy that allows for early detection of defects through unit, integration, and end-to-end (E2E) tests. However, the existing framework requires code-first developers to create automated tests, which can be a barrier for makers who may not have coding expertise.

Describe the solution you'd like

Test Case Generation

Provide a set of testing patterns and mini reference example that demonstrate automated tests using Test Engine that supports the following scenarios:

Security Related

• Security Role Checks (Non privileged person, Security Roles Checks)

Monitoring

• Health Check (For example open page and basic click checks)

App Interaction Patterns

• Ability to test Create, Update, and Delete Operations.
• Custom Toolbars.
• Web Resources with Xrm SDK.
• Web Resources that change the visibility and appearance of the form.

Async Process Testing

• Interaction with Business Process Flow.
• Trigger Power Automate Cloud Flows.
• Update Dataverse for async business processes.

The patterns should also provide guidance for implementing a shift-left testing strategy by incorporating unit, integration, and E2E tests across the Application, Dataverse, and Power Automate Cloud flows. This will enable early detection of defects and improve the overall quality of the application.

The patterns should be designed to allow makers to create automated tests without needing code-first developers. This can be achieved by providing user-friendly tools and interfaces that simplify the test creation process, making it accessible to a wider range of users.

Test Automation Maturity

Aside from the test case creation the guidance and samples could also consider:

• Test lifecycle: Example of how to:
  - Plan: Design for testability and operational health
  - Build: How to build MDA application to be testable
  - Test: Test case creation authoring
  - Deploy: How to make use of headless test execution and Power Pipeline integration
  - Monitor solution: The ability to have nightly builds and health checks
• ALM lifecycle: How to operate business approval process across environments. This should include local execution, headless test automation and business level test review approval process with test results and changes

Describe alternatives you've considered

Playwright

Additional context?

No response