SDKs
Choose a TestRelic SDK — Playwright, Appium, Maestro, pytest, Playwright (Python), DeepEval, or Appium (Python).
TestRelic ships a reporter/SDK per framework and language. Each one captures structured test analytics locally and, optionally, uploads them to the TestRelic cloud platform. Pick the one that matches your stack — the sidebar scopes itself to whichever you're browsing.
Playwright
JS/TS reporter for Playwright browser tests — navigation timelines, network stats, CI metadata.
Appium
JS/TS reporter for Appium mobile tests (Android/iOS via WebdriverIO).
Maestro
Reporter for Maestro mobile UI tests.
pytest
Python reporter for pytest suites.
Playwright (Python)
Python reporter for Playwright browser tests.
DeepEval
Python reporter bridging DeepEval LLM evaluations into TestRelic.
Appium (Python)
Python reporter for Appium mobile tests.
Package registry
| Framework | Package | Registry |
|---|---|---|
| Playwright | @testrelic/playwright-analytics | npm |
| Appium | @testrelic/appium-analytics | npm (beta) |
| Maestro | @testrelic/maestro-analytics | npm (beta) |
| pytest | testrelic-pytest | PyPI |
| Playwright (Python) | testrelic-playwright | PyPI |
| DeepEval | testrelic-deepeval | PyPI (beta) |
| Appium (Python) | testrelic-appium | PyPI (beta) |
The two families at a glance — how each package plugs into its framework and what it captures:
@testrelic/playwright-analyticsPlaywright reporter + enhanced test / API fixtures + shard merge
Navigation timelines, network stats, API tracking — unified browser + API report
@testrelic/appium-analyticsWebdriverIO service (collection) + reporter (report writing)
Device logs, WebDriver commands, network traffic, screenshots, video
@testrelic/maestro-analyticsWraps Maestro CLI flow runs
Per-step timing and parameters, assertions, optional network capture (mitmproxy / HAR)
Every SDK captures structured analytics locally first — reports stay on disk; uploading runs to the TestRelic cloud platform is optional.