Test Frameworks

Overview

TestKase supports reporting test results from a wide range of automation frameworks. Each framework guide covers full setup from scratch — installation, configuration, writing tests, generating output files — and how to integrate with the @testkase/reporter CLI.

Supported Frameworks

Web Testing

Framework	Language	Reporter Format	Guide
Jest	JavaScript	`junit` (via jest-junit)	Jest Guide
Playwright	JavaScript/TypeScript	`playwright` (native JSON)	Playwright Guide
Cypress	JavaScript	`cypress` or `junit`	Cypress Guide
Selenium	Java/Python/JS	`junit` or `testng`	Selenium Guide
WebdriverIO	JavaScript	`junit` (via wdio-junit-reporter)	WebdriverIO Guide
Mocha	JavaScript	`junit` (via mocha-junit-reporter)	Mocha Guide

Mobile Testing

Framework	Language	Reporter Format	Guide
Appium	Java/JS/Python	`junit` or `testng`	Appium Guide
Detox	JavaScript	`junit` (via jest-junit)	Detox Guide
Espresso	Kotlin/Java	`junit` (Gradle)	Espresso Guide
XCUITest	Swift	`junit` (xcresult conversion)	XCUITest Guide

Backend & General Testing

Framework	Language	Reporter Format	Guide
pytest	Python	`junit` (built-in `--junitxml`)	pytest Guide
TestNG	Java	`testng` (native XML)	TestNG Guide
NUnit	C# / .NET	`nunit` (NUnit 3 XML)	NUnit Guide

BDD Frameworks

Framework	Language	Reporter Format	Guide
Cucumber	JS/Java/Ruby	`cucumber` (JSON)	Cucumber Guide
Robot Framework	Python	`junit` (built-in `--xunit`)	Robot Framework Guide

Choosing a Format

If your framework supports multiple output formats, use the most specific one available:

Native format (playwright, cypress, testng, nunit, cucumber) — provides the richest data and most accurate ID matching.
JUnit XML — universal fallback that works with nearly every framework. Use this when no native format is available.

Not sure which format to use? Check the framework-specific guide — each one recommends the best format for TestKase integration.