Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature]: Enable Test Engine Integration with Playwright MCP Server via Test Engine MCP Server

Open
#648 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp, playwright, vscode

Research direction

The issue names no files, tests, or entry points. Start by locating the Test Engine integration surface and its existing Playwright-related session handling, then scope the MCP server, session reuse, prompt execution, and VS Code compatibility requirements; done means these four capabilities work together through a stdio-compatible interface.

Written by the indexing model from the issue text.

Description

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

Enable Power Apps Test Engine to integrate with Playwright MCP Server by exposing a stdio-compatible interface. This would allow prompt-driven test automation workflows to leverage Test Engine capabilities without requiring manual scripting in TypeScript or Power Fx.

Motivation

Current limitations in Playwright’s ability to snapshot and navigate complex iframe structures in Power Apps hinder UI automation. While Test Engine provides deep access to the JavaScript object model for entitylist and entityrecord controls, it is not currently accessible via MCP workflows.

This feature would allow users to:

  • Run tests using natural language prompts via GenAIScript, Semantic Kernel, or GenKit.
  • Reuse authentication and session state from Playwright MCP Server.
  • Automate Model Driven App testing without writing traditional test code.
  • Capture screenshots and documentation directly from VS Code using MCP agent mode
Describe the solution you'd like
  1. Expose MCP Server for Test Engine

    • Implement a stdio-compatible interface that allows Test Engine to act as an MCP server.
    • Register Test Engine capabilities as callable MCP tools with metadata (name, description, inputs/outputs).
  2. Enable Session State Reuse

    • Support persisted session state from Playwright MCP to maintain authentication across test runs.
  3. Support Prompt-Based Test Execution

    • Allow prompt-driven invocation of Test Engine features using GenAIScript or similar frameworks.
  4. VS Code Compatibility

    • Ensure Test Engine tools are discoverable and usable within VS Code’s MCP agent mode.

Benefits

  • Eliminates the need for manual scripting in Power Fx or TypeScript and leverage MCP action integration
  • Enables low-code/no-code testers to automate scenarios using natural language.
  • Bridges browser-level automation with platform-specific control access.
  • Accelerates adoption of AI-driven testing workflows.
Describe alternatives you've considered

No response

Additional context?

No response

Dominant language
C#
Stars
150
Forks
55
Avg merge
5d 23h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/PowerApps-TestEngine

All issues in microsoft/PowerApps-TestEngine

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.