agentsclimarketplace
Sign in

Execute test

Skill katalon-labs/true-skills/plugins/katalon-true-platform/skills/execute-test

Execute Katalon True Platform/TestOps tests when the input is an existing test case, manual test case list, test suite, suite collection, execution request, or "run with AI" instruction. Use when you need to create a manual test run, start Run with AI, poll AI session results, schedule automated suites, read execution/test results, or summarize pass/fail/blocked outcomes. For full requirement-to-test-design-to-execution workflows, combine with or defer to true-platform-testing. Written for the manual tester who has cases and needs a result, by hand or through Run with AI. A coded suite driven from a framework starts at playwright-execute or upload-report.From its SKILL.md

Install
npx -y skills add katalon-labs/true-skills --skill execute-test

Assembled 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

4.4 KB, as published. Nobody here has run it

Katalon Execute Test

Use this skill for running already-selected Katalon test cases or suites and reporting execution outcomes. Keep the larger true-platform-testing skill as the end-to-end orchestrator; this skill is the focused execution workflow.

Availability Boundary

State the execution boundary before running:

  • Available: read AUT environments, create manual test runs, start Run with AI, poll AI sessions, schedule automated suite runs, and read execution/test results.
  • Not directly available: guarantee AI completion, inspect the live AUT UI through Katalon MCP, or run manual test cases through the automated scheduler.
  • Use Browser/Playwright only when AUT exploration or visual verification outside Katalon MCP is needed.

Read references/capability-boundaries.md when capability scope is unclear.

Resolve Context First

Before creating or scheduling any run:

  1. Call list_projects.
  2. Call list_repositories.
  3. Resolve the repository/Test Project from the user's wording or unique available repository.

Ask only when multiple equally valid repositories remain, required credentials are missing, or the next action is destructive.

Choose Execution Type

Use manual execution when:

  • The user provides manual test cases.
  • The user asks for Run with AI.
  • The test cases were just created in Katalon.
  • The input is a manual suite.

Use automated execution only when the input is an automated suite or suite collection.

If the user only says "run tests" and the type cannot be inferred, ask whether they want manual or automated execution.

Manual Run With AI

Always follow this order:

  1. Call read_auts immediately before create_manual_test_run.
  2. Resolve the manual cases or suites.
  3. If a suite is provided, call read_test_suite before creating the run.
  4. If individual cases are provided, call read_test_case for unclear or risky inputs.
  5. Create the manual run with create_manual_test_run.
  6. Start Run with AI automatically with create_manual_ai_session unless the user explicitly says not to run AI.
  7. Poll read_manual_ai_session until all items leave TODO/IN_TESTING, or the platform returns an external timeout/error.
  8. Read available execution/test result details before responding.

AUT rules:

  • Never reuse AUT environment selection from an earlier turn or earlier run.
  • Choose the AUT/environment whose URL or name clearly matches the target AUT.
  • If no AUT exists and a URL is known from the user, requirement, or test data, use it as default_aut_environment_url.
  • Ask only when multiple AUTs are equally plausible or no target URL can be resolved.

Read references/execution-workflow.md before creating manual executions.

Automated Execution

Use automated execution only for automated suites:

  1. Find automated suites or suite collections with find_test_suites.
  2. Find execution profiles with find_execution_profiles.
  3. Find TestCloud environments with list_test_cloud_environments.
  4. Build the run configuration with build_run_configuration.
  5. Optionally build a schedule with build_schedule.
  6. Run with schedule_test_run.
  7. Read execution and test results with read_execution, read_execution_test_results, and read_test_result as needed.

Do not call create_manual_test_run for automated suites, and do not call schedule_test_run for individual manual test cases.

Report Results

After execution, report:

  • Run name and link when returned.
  • Final status.
  • Passed, failed, blocked/incomplete, and not-run counts.
  • Failed cases with concise failure reasons.
  • Defects created or recommended.
  • Gaps, skipped cases, and manual follow-up required.

Ask before creating ALM-linked defects unless the user explicitly requested defect creation for failures.

What ships with it: 3 files

4.6 KB alongside SKILL.md

agents/

references/

Gives 0 of the 12 instructions most test skills give

Counted across 1,201 of the 2,096 authors here whose files we hold, read 2026-09-06

  • Write a failing test before writing codein 43 of 1201, across 36 files
  • Run the full test suitein 36 of 1201, across 35 files
  • Test only one variable per experimentin 34 of 1201, across 17 files
  • Read product marketing context before asking questionsin 34 of 1201, across 14 files
  • Mock external dependenciesin 34 of 1201, across 30 files
  • Define primary, secondary, and guardrail metricsin 33 of 1201, across 16 files
  • Pre-determine sample size before startingin 31 of 1201, across 14 files
  • Test behavior rather than implementationin 31 of 1201, across 29 files
  • Formulate a hypothesis before designing a testin 30 of 1201, across 13 files
  • Document every test hypothesis, variant, and resultin 29 of 1201, across 11 files
  • Use descriptive test function namesin 25 of 1201, across 21 files
  • Commit to the methodology without stopping earlyin 24 of 1201, across 8 files

Said here and by no other author read

  • start Run with AI automatically after manual test creation
  • poll AI sessions until completion
  • Call list_projects and list_repositories before mutating data
  • Resolve repository from user input or requirement key
  • Verify test suites with read_test_suite after changes
  • Call read_auts before creating manual test runs

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 625,150. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.