ChainTest reporting for Katalon Studio: a bridge I built because nothing else exists
Katalon Studio has no ChainTest integration right now, official or community. ChainTest publishes plugins for TestNG, JUnit5, and Cucumber, and that’s it. If you wanted its dashboards, or even just a clean report format, inside Katalon, the only option was writing a Test Listener against ChainTest’s plugin API by hand and figuring out its jar dependencies yourself.
I ran into this on a project and built the missing piece instead of working around it.
What it does
chaintest-katalon-bridge installs into an existing Katalon project with a single command. No plugin from the Katalon Store, no Test Listener code to write, no changes to your existing Test Cases or Test Suites. Once installed, every Test Suite run produces a static HTML report on its own, without you configuring anything.
If you want more than a static report, there’s an optional add-on called ChainLP: a small Docker Compose stack that gives you build history, pass rate trends, and a real dashboard across runs. It’s off by default, purely optional.
A few other things it includes:
- Cross platform installers for Windows, macOS, and Linux, including double click install/uninstall
- Ready to use CI templates for GitLab CI and Azure Pipelines
- A minimal, verified jar set. ChainTest’s own dependencies pull in AWS S3 and Azure Blob Storage SDKs that most people never touch, and this bridge deliberately leaves those out
How to install
npx chaintest-katalon-bridge install "/path/to/your/katalon/project"
Or install it once and reuse it:
npm install -g chaintest-katalon-bridge
chaintest-katalon-bridge install "/path/to/your/katalon/project"
Marketplace: https://github.com/marketplace/actions/chaintest-katalon-bridge
npm: https://www.npmjs.com/package/chaintest-katalon-bridge
GitHub: https://github.com/montbaga/chaintest-katalon-bridge
The README covers install and uninstall for every platform. There’s a separate guide in the repo for setting up ChainLP, covering everything from running it on your own laptop to a shared setup for a whole team with CI pushing results into it.
This is version 1.0.2, built solo, so there will be rough edges I haven’t hit yet. If you try it and something breaks, open an issue on GitHub, I’d rather know now than have people quietly avoid it. Questions welcome here too.