Your stack stays your stack.
Sign-in, issue tracking, reporting, dashboards, and pipelines — RobusTest meets each one where it already lives. Results flow out to the tools your team watches; jobs flow in from the CI you already run.
One click in, with the accounts you issue.
Single sign-on
- OAuth2 sign-in with Google Workspace and Microsoft accounts
- Domain-restricted signup — only your email domains can create accounts
- Email/password accounts with confirmation, recovery, and lockout for teams without an identity provider
Teams & keys
- Roles, profiles, and groups for administration; project-based teams with members and admins
- Per-user API access keys for scripted and CI access — revocable and regenerable at any time
- Admin views of live sessions and monthly usage per user
Results land where your team already looks.
JIRA
File a JIRA issue straight from a failed test result — device, build, and logs attached. JIRA connections are configured per project.
ReportPortal
A ReportPortal-compatible ingestion API mirrors the full launch, item, and log lifecycle, so runs appear in ReportPortal as if they ran there.
JUnit & HTML
Every job exports JUnit XML for CI test tabs, alongside the platform's own HTML reports with screenshots, logs, and timing analysis.
InfluxDB
Test results and performance records stream to InfluxDB, ready for the Grafana dashboards your team already maintains.
Hear about it without watching for it.
Job finished, run failed, device went offline — the events you care about reach the channel you actually read.
- Slack messages via incoming webhooks, configured per job or per project
- Email to any recipient list
- Generic REST webhooks with custom headers for anything else — pagers, chat tools, internal services
- An event trigger engine that fires actions on job, build, and device events
Trigger from any pipeline that can curl.
A documented public API — authenticated with per-user access keys — triggers jobs, polls status, and fetches results and devices. It runs in production at large customers today, from Jenkins, GitHub Actions, GitLab CI, and plain shell scripts.
Trigger
Kick off a job against a device query — "all Android 13+ with SIM" — with the build you just produced.
Poll
Watch job status and per-device instances from the pipeline; abort from the same API if a newer commit supersedes the run.
Collect
Pull JUnit for the CI test tab and link back to full reports, screenshots, and logs in the lab.
Kubernetes-backed job runners can scale execution environments on your cluster. @components.Beta()
Wire the lab into your workflow.
Tell us what your team uses for sign-in, tickets, and CI — we'll show the lab feeding all three in one demo.