BDD specifications and automated test results in a single dashboard. Everyone — from Product Owners to Automation Engineers — sees the same truth.
Specs and results in one place — no gap between what's defined and what's tested
Submit JUnit XML results directly from your pipeline. GitHub Actions, Jenkins, GitLab CI, Azure DevOps — one API call and results are live.
Pass rates, failure trends, and quality regressions across builds. Time-series charts that show if quality is going up or down.
Generate executable .feature files from your BDD specs. Works with Cucumber, SpecFlow, and any Gherkin-compatible framework.
Share projects, manage permissions by role. Product owners, QA, dev, and automation all work in the same space.
Define. Execute. Analyze.
Write 4-level BDD specs collaboratively. Each role fills in their level:
Feature: Checkout
L1 Business: PO defines requirements
L2 Functional: QA writes Given/When/Then
L3 Technical: Dev adds API contracts
L4 Automation: AE links test scripts
Run tests with your framework, submit JUnit XML results via API. One curl command in your CI/CD pipeline.
# GitHub Actions step
- run: |
curl -X POST \
$SHIPQA_URL/api/results \
-H "X-Api-Key: $KEY" \
-F "file=@results.xml"
View dashboards, track trends, catch regressions before they reach production.
Pass rate: 91% → 96%
Tests: 312 passing
Failures: 3 → 0
Trend: ▲ improving
The only platform where specs and results live together
No other platform offers hierarchical BDD where each stakeholder contributes at their level of detail.
No gap between what's defined and what's tested. Requirements and automation results side by side.
API-key authenticated test ingestion. No manual uploads, no browser plugins — just a curl in your CI.
JUnit XML in, Gherkin out. Works with Cucumber, SpecFlow, Robot Framework, pytest, Jest — anything that outputs JUnit.
Any CI/CD system that runs tests can send results to ShipQA
Specs, results, and trends — one dashboard for the whole team