Understanding Test Engine providers (preview)

Test Engine uses a provider-based architecture that allows it to support testing across different application types. Each provider is optimized for a specific application type, allowing for efficient test automation while providing a consistent testing experience.

What are providers?

Providers are specialized modules within Test Engine that handle the specifics of interacting with different application types:

• They abstract the complexity of testing different application technologies
• They provide type-specific implementation of testing actions
• They handle authentication and context appropriately for each application type
• They determine how tests are executed and interpreted

Provider types

The following sections describe the different types of providers available in Test Engine. Each provider is designed for a specific application scenario, offering tailored capabilities for web-based, and API-based testing.

Web-based providers

Web-based providers extend Playwright's browser automation capabilities by adding application-specific abstractions, making it easier to test web applications without dealing with low-level DOM elements.

Canvas application provider

The Canvas Application Provider (canvas) is specialized for testing Power Apps canvas applications:

• Abstraction Level: Works with control names as defined in the app maker studio
• Technology: Extends Playwright for browser-based automation
• Key Capabilities:
  • Accesses canvas app controls by logical names
  • Handles canvas-specific control types and events
  • Supports gallery control navigation and interaction

Command Example:

pac test run `
   --provider canvas `
   --test-plan-file your-testplan.te.yaml `
   --tenant your-tenantid-guid-value `
   --environment-id your-environmentid-guid-value

Learn more about testing canvas applications.

Model-driven application provider

The Model-driven Application Provider (mda) is specialized for Dataverse model-driven applications:

• Abstraction Level: Works with model-driven application elements like forms, views, and business process flows
• Technology: Extends Playwright for browser-based automation
• Key Capabilities:
  • Navigates complex model-driven app interfaces
  • Handles form data entry and validation
  • Supports entity record operations

Command Example:

pac test run `
   --provider mda `
   --test-plan-file your-testplan.te.yaml `
   --tenant your-tenantid-guid-value `
   --environment-id your-environmentid-guid-value `
   --domain "https://contoso.crm.dynamics.com/main.aspx?appid=00001111-aaaa-2222-bbbb-3333cccc4444&pagetype=entityrecord&etn=account"

Learn more about testing model-driven applications.

API-based providers

API-based providers interact directly with backend services without necessarily using a browser interface.

Power Fx provider

The Power Fx Provider (powerfx) allows direct execution of Power Fx formulas, useful for Dataverse integration testing:

• Authentication: Uses OAuth tokens obtained via Azure CLI az login command
• Technology: Directly calls Dataverse API endpoints
• Key Capabilities:
  • Performs CRUD operations on Dataverse tables
  • Executes business logic without UI interaction
  • Enables focused integration testing

Command Example:

pac test run `
   --provider powerfx `
   --test-plan-file your-testplan.te.yaml `
   --tenant your-tenantid-guid-value `
   --environment-id your-environmentid-guid-value `
   --domain "https://contoso.crm.dynamics.com"

Learn more about testing Dataverse extensions.

Technical implementation

The following sections explain the underlying architecture, authentication flows, and Dataverse integration for Test Engine providers. Understanding these details help you configure and extend providers for your specific testing needs.

Architecture

Test Engine's provider architecture follows a layered approach:

1. Core Engine Layer: Contains shared functionality across all providers
2. Provider Layer: Implements application-specific testing logic
3. Authentication Layer: Handles identity and security context
4. Extension Layer: Allows custom functionality to be added

Authentication flow

Providers use different authentication flows based on their requirements:

• Web Providers (Canvas, Model-driven): Use browser-based authentication with storage state
• API Providers (Power Fx): Use OAuth tokens from Azure CLI for direct API access

Dataverse integration

All providers can benefit from Dataverse integration, which enables:

• Direct table access via Power Fx functions
• Data seeding and cleanup operations
• Verification of backend state changes

To enable Dataverse integration, add the following to your test settings:

testSettings:
  extensionModules:
    enable: true
    parameters:
      enableDataverseFunctions: true

Learn how to test Dataverse extensions

Choosing the right provider

Select a provider based on your application type and testing requirements:

Application Type	Provider	Best For
Canvas apps	canvas	UI testing, control interaction, screen navigation
Model-driven apps	mda	Forms, views, business process flows, entity operations
Pure Dataverse integration	powerfx	Backend logic, table operations, plugin validation

Related articles

Test canvas applications
Test model-driven applications
Test Dataverse extensions
Test Engine Extensibility
Test Engine and Playwright