Free, open-source Allure reporting for Katalon Studio : no plugin, zero test-script changes

Thanks @dineshh :folded_hands:

Major Release - 2.0.0

Allure-katalon-bridge 2.0.0

This release works through the Allure team’s review of 1.0.4. Reports are
more accurate, more of Katalon’s own data reaches them, and the bridge now
works with Allure TestOps reruns.

Upgrade

npx allure-katalon-bridge install "<path to your Katalon project>"

Your existing allure.properties is kept. New settings use their defaults,
so nothing needs to change. Requires the Allure 2 commandline
(npm install -g allure-commandline). GitHub Action users get 2.0.0
automatically.

Fixed

  • Repeated test cases were merged into one. A test case used in several
    suites, or a suite run twice in a collection, now shows once per run
    instead of as “retries” of one test.
  • Manual steps disappeared. AllureKeywords.step() steps and anything
    attached inside them now stay in the report.
  • A crashed @SetUp gave an empty, green-looking report. A failed suite
    @SetUp or @TearDown now shows as a broken result with the stack trace.
  • No history or trend with the default single-file report. History and
    trend now build up run after run, per suite or collection, and local runs
    are numbered.
  • Allure 3 failed silently. The bridge now detects Allure 3 and says so in
    the console, and its messages (“report ready”, warnings) now show in the
    Katalon console and CI logs.
  • Parallel-execution suites lost results when the results folder was set
    through ALLURE_RESULTS_DIR or allure.properties. They now land in the
    configured folder.

New

  • Katalon’s own fields in the report: test case Description, Tags
    (allure.label.owner:jane, allure.label.severity:critical, plain tags)
    and Variables as parameters, with masked variables shown as ******.
  • Better failure evidence: the page source next to the screenshot, the
    screenshot Katalon took on the failed step, and screenshots for Mobile tests.
  • API tests: each request and response is attached, with auth headers,
    cookies and password/token fields masked.
  • Markers and links: flaky() / muted() / known(), and short issue/TMS
    links (issue('BUG-12')) from a pattern in allure.properties.
  • Allure TestOps: rerunning selected tests from TestOps runs only those.
    See the README’s “Allure TestOps” section and
    testops-github-actions.example.yml.
  • browser, os and device labels.

Worth knowing

  • The Suites tree is now Collection > Suite > Browser. The browser is no
    longer part of the suite name.
  • On Allure 2.44 and later, and in Allure TestOps, history starts fresh once
    for test cases that run in more than one suite. Earlier Allure 2 versions
    keep their history.
  • Page source on failure, API request attachments and test plans are on by
    default. Each has a setting to switch it off (see Configuration in the
    README).

v 2.1.0 released , fixed the below bugs

  • Test identity is now the test suite and test case. Browser and execution
    profile are parameters, so reordering a collection keeps each browser’s
    own history.
  • New setting allure.parameters.excluded=orderId,timestamp for variables
    that change every run, so they don’t reset a test’s history.