Katalon TestOps-After JIRA testcase moved to TestOps, there is a run button .what is the purpose of 'Run' button in testcase

Product Forums Katalon TestOps
, , ,
1

Hi,

I’m currently exploring JIRA TestOps integration feature and
I have an questions in Testcases part

1.After integrating and moving the Generated manual testcases from JIRA to Katalon TestOps, the testcases are displayed and on clicking individual testcase there is an ‘Run’ button as below screenshot. What is the purpose of that, how it can running without script

image
image1852×353 27.3 KB

@Elly_Tran

1 Like
2

The Run button in Katalon TestOps for manual test cases imported from Jira allows you to execute and track manual test runs directly within TestOps.

Purpose of the “Run” Button

  1. Manual Test Execution:
  • The button lets you record manual test executions (pass/fail status, notes, attachments) for the imported Jira test case.
  • It does not run automated scripts unless explicitly linked (see below).
  1. Test Cycle Integration:
  • When clicked, it creates an ad-hoc test run in TestOps’ Test Execution module.
  • Results sync back to Jira if integration is configured.

How It Works Without Scripts

  1. Manual Process:
  • Click Run > Assign to yourself or a team member.
  • A manual test session opens where you can:
    • Mark steps as Passed/Failed.
    • Add comments/screenshots.
    • Log defects to Jira.

java

// Example flow (no code needed):
1. Click "Run" → "Start Manual Execution".
2. Follow test steps manually.
3. Record results in TestOps UI.
  1. Traceability:
  • Results are tracked in TestOps > Reports and reflected in Jira.

Linking Automation Later

To automate the test case:

  1. Link to a Katalon Studio Script:
  • In TestOps, edit the test case > Automation tab.
  • Map it to an existing automated test script (e.g., VerifyLogin).

groovy

// TestOps will associate manual test case ID with automated script:
@TestCaseId("JIRA-123") // Match Jira test case key
def "Verify Login"() {
  // Automation steps
}
  1. Run Automated Tests:
  • After linking, use Scheduled Runs or CI/CD pipelines to execute the script.
  • Results auto-populate in TestOps/Jira.

Key Scenarios

Scenario “Run” Button Behavior
Manual Test Records manual execution results.
Automated Test (Linked) Triggers script via CI/CD (not direct execution).

When to Use

  • Manual Testing Phase: Use the button for exploratory/manual runs.
  • Automation Transition: Keep using it while building automation scripts.
4

Hi @vasanthi.jayakumar,

Thank you for letting us know. I will ask my team to check on it and back here soon