Playwright execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded Katalon Platform runs or reports. Written for the automation tester who wants the suite driven and the results landed in the platform in one step. For a report from a run that has already finished, or from any other framework, use upload-report.From its SKILL.md
npx -y skills add katalon-labs/true-skills --skill playwright-executeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
6.2 KB, as published. Nobody here has run it
Katalon Playwright Execute
Use this skill when the user asks to execute a Playwright script/suite and send results to Katalon True Platform. The workflow is not complete until local execution finishes, report artifacts are collected, and upload is either verified or clearly blocked.
Execution Workflow
+------------------+ --> +------------------+ --> +------------------+
| Resolve target | | Preflight repo | | Configure report |
+------------------+ +------------------+ +------------------+
|
v
+------------------+ <-- +------------------+ <-- +------------------+
| Verify Platform | | Upload report | | Run Playwright |
+------------------+ +------------------+ +------------------+
Required Context
Resolve or ask for only missing required values:
- Playwright target: spec file, grep, project, package script, suite command, or user-provided command.
- Repository/root directory that contains
package.jsonand Playwright config. - Katalon Platform project ID. Use Katalon MCP
list_projectswhen available. - Katalon API key from a secure source such as
KATALON_API_KEY; check whether it is already available before asking. - Platform base URL only when non-default or when the project uses QA/prod custom domains.
- Whether the agent may modify Playwright config/package files if the Katalon reporter is missing.
Treat the human as a tool: ask concise questions when target, credentials, project, or permission cannot be resolved safely. Never ask the user to paste secrets into normal chat when a secure secret mechanism or environment variable can be used.
Preflight
Before running:
- Inspect the repository for
package.json,playwright.config.*,@playwright/test, existing reporters, package manager lockfiles, and scripts. - Verify Node.js is version 18 or newer when possible.
- Check for
KATALON_API_KEYin the current process environment or the repo's approved secret mechanism before composing any upload command. - If
KATALON_API_KEYis missing, stop before execution/upload and ask the user to provide it through a secure environment variable or secret mechanism. - Run dependency installation only when the repo convention is clear and the user has allowed dependency changes.
- Confirm
@katalon/playwright-reporteris installed or can be installed. - Verify a deterministic report output directory, preferably
./reportsor the repo's existing Katalon report directory. - Build commands with secrets redacted in user-facing output.
Read references/playwright-katalon-reporting.md before editing config or composing upload commands.
Configure Reporter
Prefer the existing project convention. If the Katalon reporter is absent and the user allowed edits:
- Add
@katalon/playwright-reporteras a dev dependency. - Add
getGlobalSetupPath()from@katalon/playwright-reporterto PlaywrightglobalSetupunless the existing config already has a global setup that must be preserved. - Add the Katalon reporter with
outputDir. - Configure platform upload through environment variables, not hard-coded values.
- Preserve existing reporters such as
list,html,junit, or custom reporters.
Do not overwrite unrelated Playwright projects, retries, timeouts, use settings, web servers, or CI-specific behavior.
Run And Upload
Use one of these modes:
- Upload during execution: set
KATALON_API_KEYandKATALON_PROJECT_ID, then run the selected Playwright command. - Separate upload: run Playwright to generate report files, then run
playwright-reporter upload. - Existing report upload: skip execution only when the user explicitly provides an existing Playwright reporter output directory.
Prefer upload during execution when the project already has the Katalon reporter configured. Prefer separate upload when the user asks to run first, upload later, or when troubleshooting import failures.
If the Playwright command fails after generating report artifacts, still attempt upload when the reporter output exists unless the user asked to skip upload on failure. Test failures are valid report data.
Platform Verification
After upload:
- Use Katalon MCP tools to list/read recent executions, test results, or quality data when available.
- Match by project ID, run time, test names, and framework metadata.
- Resolve the Platform result URL from reporter output, upload output, MCP execution data, or the known project/execution path.
- Always provide the best available Platform result URL so the user can open the uploaded run/report.
- If MCP cannot verify, inspect CLI output for upload success and report that Platform verification is blocked.
- If upload is asynchronous/importing, poll when a read/list tool exists; otherwise report the importing state.
Response Contract
Report:
- Playwright command run and exit status, with secrets redacted.
- Katalon upload mode: during execution, separate upload, or existing report upload.
- Local report output directory and key artifacts.
- Platform upload status: verified, importing, failed, or not verifiable.
- Platform report/run URL for the user to open when returned or discoverable; if no exact URL is available, provide the closest project reports/executions URL and state why it is not exact.
- Passed, failed, skipped, and timed-out counts when available.
- Failed tests with concise reasons.
- Any required follow-up: missing API key, missing project ID, install blocked, config permission missing, upload failed, or MCP verification unavailable.
Do not claim success if Playwright ran locally but the Katalon upload did not happen or cannot be verified.
What ships with it: 1 file
4.5 KB alongside SKILL.md
references/
Gives 0 of the 12 instructions most e2e browser skills give
Counted across 499 of the 513 authors here whose files we hold, read 2026-09-06
- Capture screenshots, videos, and traces on failurein 32 of 499, across 23 files
- Close the browser when donein 22 of 499
- Interact with elements using snapshot refsin 21 of 499, across 20 files
- Wait for specific network responses instead of fixed timeoutsin 20 of 499, across 10 files
- Keep tests independent with no shared statein 19 of 499, across 17 files
- Use Page Object Model classes to encapsulate page interactionsin 19 of 499, across 9 files
- Locate elements with data-testid attributesin 19 of 499, across 10 files
- Quarantine flaky tests with fixme or skipin 17 of 499, across 7 files
- Upload test artifacts after every CI runin 17 of 499, across 8 files
- Wait on conditions instead of using fixed sleepsin 17 of 499, across 13 files
- Clean up test data after each testin 17 of 499, across 16 files
- Test user-visible behavior, not implementation detailsin 16 of 499, across 10 files
Said here and by no other author read
- resolve or ask for missing required context before running
- verify the API key exists before composing upload commands
- stop and ask via secure channel if the key is missing
- inspect the repository for config, scripts, and existing reporters
- read the reporting reference before editing config or uploading
- add the Katalon reporter only when the user allows edits
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.