Playwright Test Executor – Message
The Playwright Test Executor integrates browser-based UI testing directly into your automation workflow. It executes specified Playwright TypeScript test files, drives browser interactions, and returns structured test results as a Message output, ready for downstream processing without manual intervention.
Key Capabilities
UI Validation: Automates validation of web applications directly within your workflow
Test Execution: Runs Playwright TypeScript test files from any workflow environment
Structured Output: Returns pass/fail results, execution logs, and error details
MCP Integration: Works natively with the Playwright MCP Server Tool
Note: The Playwright MCP Server must be configured and active in your workflow before using this component.
Parameter
| Parameter | Description |
|---|---|
| Test file path | Provide the path to the Playwright test file or folder to execute. Must end with .spec.ts — for example, tests/example.spec.ts. |
Output
| Output | Description |
|---|---|
| Execution Output | Returns the step-by-step execution details of the test cases and error details for any failures during testcase generation. |
Tool Mode
In Tool Mode, the Playwright Test Executor generates a standardized, slug-based output that uniquely identifies the component within your workflow. This slug allows the agent to invoke the component programmatically, ensuring tests are triggered accurately and workflow execution stays seamless.
Demo Slug
demo_test_execute – Triggers the Playwright test execution, running browser interactions against the target application and returning pass/fail status, execution logs, and any error details captured during the run.
Workflow Sequence
1. Enable Tool Mode in the Playwright Test Executor component.
2. Connect the component’s tool node to the agent’s tool node.
3. Provide the test file path as input.
4. Instruct the agent to perform the required testing task.
5. The agent invokes demo_test_execute and returns structured results.
Agent Usage
The agent interacts with your test suite using this demo slug.
Example:
Input: https://www.adidas.co.in/
Instruction: “Create and execute 15 test cases for the front page.”
Output: Pass/fail status, execution logs, and error details for each of the 15 test cases.
Best Practices
1. Enable Tool Mode and connect to the agent – Use the Playwright MCP Server tool to execute the flow, enable it in Tool Mode, and connect it to the agent.
2. Provide the correct test file path – Ensure the input path ends with .spec.ts so the agent references the correct test file.
3. Use unique slugs for multiple components – If your workflow includes more than one Playwright Test Executor, assign distinct demo slugs to each so the agent references the correct instance.
