Migrate from Power Apps Test Engine

Power Apps Test Engine uses YAML-based test definitions that run against a specialized test host. Power Platform Playwright samples use TypeScript and the standard Playwright test runner, giving you access to the full Playwright API, ecosystem tooling, and CI/CD integrations.

This guide maps Test Engine concepts to their Playwright equivalents and walks through a concrete migration example.

Concept mapping

The following table shows how Test Engine concepts map to their Playwright equivalents.

Before you begin

Complete these prerequisites before starting the migration.

1. Clone the repository and install dependencies:

   git clone https://github.com/microsoft/power-platform-playwright-samples.git
   cd power-platform-playwright-samples
   node common/scripts/install-run-rush.js install
   

2. Copy your app URL from the Test Engine YAML appLogicalName or the Power Apps make portal.

3. Set up authentication - see Authentication guide.

Step 1: Identify your app type

Test Engine supports canvas apps. If you're migrating:

• Canvas app tests → Follow Test canvas apps.
• Custom page tests → Follow Test custom pages.
• Model-driven app tests → Follow Test model-driven apps.

Step 2: Map your test structure

Test Engine YAML

A typical Test Engine test definition looks like this.

testSuite:
  testSuiteName: OrdersTests
  testCases:
    - testCaseName: CreateOrder
      testSteps: |
        Select(AddButton);
        SetProperty(OrderNumberInput, "ORD-TEST");
        Select(SaveButton);
        Assert(Label1.Text = "Saved");

Playwright TypeScript equivalent

Here's the same test rewritten by using Playwright and the Power Platform toolkit.

import { test, expect } from '@playwright/test';
import { AppProvider, AppType, AppLaunchMode, buildCanvasAppUrlFromEnv } from 'power-platform-playwright-toolkit';

test.describe('OrdersTests', () => {
  test('CreateOrder', async ({ page, context }) => {
    const app = new AppProvider(page, context);
    await app.launch({
      app: 'Orders App',
      type: AppType.Canvas,
      mode: AppLaunchMode.Play,
      skipMakerPortal: true,
      directUrl: buildCanvasAppUrlFromEnv(),
    });

    const canvasFrame = page.frameLocator('iframe[name="fullscreen-app-host"]');

    // Wait for app to load
    await canvasFrame
      .locator('[data-control-part="gallery-item"]')
      .first()
      .waitFor({ state: 'visible', timeout: 60000 });

    // Select(AddButton)
    await canvasFrame.locator('[data-control-name="AddButton"] [role="button"]').click();

    // SetProperty(OrderNumberInput, "ORD-TEST")
    await canvasFrame.locator('input[aria-label="Order Number"]').fill('ORD-TEST');

    // Select(SaveButton)
    await canvasFrame.locator('[data-control-name="SaveButton"] [role="button"]').click();

    // Assert(Label1.Text = "Saved")
    await expect(canvasFrame.locator('[data-control-name="Label1"]')).toHaveText('Saved');
  });
});

Step 3: Map control selectors

Test Engine uses control names from Power Apps Studio directly in YAML. In Playwright, use data-control-name attributes with the same values:

Step 4: Map environment variables

Test Engine uses an environmentVariables section in YAML. Move these values to your .env file:

# Test Engine YAML
environmentVariables:
  - name: appUrl
    value: https://apps.powerapps.com/play/...

# packages/e2e-tests/.env
CANVAS_APP_URL=https://apps.powerapps.com/play/...

Step 5: Map setup and teardown

Convert Test Engine lifecycle hooks to Playwright's built-in beforeEach and afterEach functions.

# Test Engine
testSuite:
  onTestCaseStart: |
    Navigate(HomeScreen);

// Playwright
test.beforeEach(async ({ page, context }) => {
  // Re-launch the app for each test (equivalent to onTestCaseStart navigation)
  const app = new AppProvider(page, context);
  await app.launch({ ... });
});

Step 6: Replace Power Fx assertions

Test Engine uses Power Fx expressions in Assert(). Replace with Playwright expect() assertions:

Key differences to be aware of

Keep these behavioral differences in mind as you migrate your tests.

Run your migrated tests

After migrating your tests, authenticate and run them by using these commands.

cd packages/e2e-tests
npm run auth:headful      # authenticate
npx playwright test       # run all tests
npx playwright test --ui  # run with interactive UI

Troubleshoot migration issues

Refer to the following table for common migration problems and their solutions.

Next steps

• Test canvas apps
• Test model-driven apps
• Sample tests

See also

• Get started
• Authentication guide
• Page Object Model