After analysis completes, you can export results in a range of formats — from human-readable Markdown to structured imports for Jira, TestRail, Azure Test Plans, and BDD tools. Choose your format before running analysis, or change it afterward and re-export.
Documentation
Data export
Integrations
BDD / Specs
Markdown
Clean, readable documentation you can commit to a repository, paste into a wiki, or share with your team. Sections are organized with headings, user story templates in bold, acceptance criteria as checkboxes, and test steps as numbered lists.File extension: .md# User Stories
## Feature: User Authentication
### US-001: User Login
**As a** registered user
**I want to** log in with my email and password
**So that** I can access my dashboard
#### Acceptance Criteria
- [ ] User can enter email and password
- [ ] Invalid credentials show error message
- [ ] Successful login redirects to dashboard
# Test Cases
## TC-001: Valid Login
**Priority:** High | **Type:** Functional
**Steps:**
1. Navigate to /login
2. Enter email: test@example.com
3. Enter password: ValidPass123
4. Click "Sign In" button
**Expected Result:**
User is redirected to /dashboard
HTML Report
A self-contained HTML document with inline styles, collapsible sections, priority indicators, and a table of contents. Print-friendly and requires no external dependencies.File extension: .htmlJSON
A structured JSON object containing metadata, user stories, test cases, and acceptance criteria. Use this format when you want to process results programmatically or import them into a custom tool.File extension: .json{
"metadata": {
"generatedAt": "2024-01-15T10:30:00Z",
"source": "ORIZON QA Analyzer",
"version": "1.0"
},
"userStories": [
{
"id": "US-001",
"title": "User Login",
"role": "registered user",
"goal": "log in with email and password",
"benefit": "access my dashboard",
"priority": "high",
"acceptanceCriteria": [
"User can enter email and password",
"Invalid credentials show error message"
]
}
],
"testCases": [
{
"id": "TC-001",
"title": "Valid Login",
"priority": "high",
"type": "functional",
"steps": [
{ "step": 1, "action": "Navigate to /login", "expected": "Login page displays" },
{ "step": 2, "action": "Enter valid credentials", "expected": "Fields populated" },
{ "step": 3, "action": "Click Sign In", "expected": "Redirect to dashboard" }
],
"expectedResult": "User is logged in and sees dashboard"
}
]
}
YAML
The same structured data as JSON, formatted in YAML. Useful for configuration-driven pipelines or tools that prefer YAML over JSON.File extension: .yaml
CSV Spreadsheet
A comma-separated file with columns for ID, Type, Title, Description, Priority, Steps, Expected Result, and Tags. Import directly into Excel or Google Sheets.File extension: .csv"ID","Type","Title","Description","Priority","Steps","Expected Result","Tags"
"TC-001","Functional","Valid Login","Verify login with valid credentials","High","1. Navigate to /login|2. Enter email|3. Click Sign In","User sees dashboard","auth,smoke"
Jira markup
Jira wiki markup formatted for direct copy-paste into Jira issues or Confluence pages. Uses Jira heading syntax (h1., h2.), table markup for test step details, and *bold* for field labels.File extension: .txth1. Test Cases
h2. TC-001: Valid Login
||Field||Value||
|Priority|High|
|Type|Functional|
h3. Test Steps
||Step||Action||Expected Result||
|1|Navigate to /login|Login page displays|
|2|Enter email: test@example.com|Email field populated|
|3|Click "Sign In" button|Redirect to dashboard|
Xray JSON
The Xray test case import format for Jira. Each test case is structured with testInfo, step-level action, data, and result fields, and labels for tagging. Import directly via the Xray import API or the Jira UI.File extension: .json{
"testInfo": {
"projectKey": "PROJ",
"summary": "Valid Login Test",
"type": "Manual",
"steps": [
{
"action": "Navigate to /login",
"data": "",
"result": "Login page is displayed"
},
{
"action": "Enter email: {{email}}",
"data": "test@example.com",
"result": "Email field shows the entered value"
}
],
"labels": ["authentication", "smoke"]
}
}
TestRail CSV
A CSV formatted for TestRail’s case import. Columns match TestRail’s required fields: Title, Section, Template, Type, Priority, Preconditions, Steps, Expected Result, and References.File extension: .csv"Title","Section","Template","Type","Priority","Steps","Expected Result"
"Valid Login","Authentication","Test Case (Steps)","Functional","High","Step 1: Navigate to /login
Step 2: Enter valid credentials
Step 3: Click Sign In","User redirected to dashboard"
Azure DevOps CSV
A CSV formatted for Azure Test Plans import. Steps are encoded in the XML format Azure expects. Priority uses Azure’s 1–4 numeric scale (1 = Critical, 2 = High, 3 = Medium, 4 = Low). Tags are semicolon-separated.File extension: .csvGherkin (Cucumber)
.feature files following Cucumber and Behave conventions. Includes feature-level tags, a narrative (As a / I want to / So that), a Background for shared setup, individual Scenario blocks, and Scenario Outline with Examples tables for data-driven tests.File extension: .feature@authentication @critical
Feature: User Authentication
As a registered user
I want to log in with my credentials
So that I can access my personalized dashboard
Background:
Given I am on the login page
@smoke @happy-path
Scenario: Successful login with valid credentials
When I enter email "test@example.com"
And I enter password "ValidPass123"
And I click the "Sign In" button
Then I should be redirected to the dashboard
@negative
Scenario: Failed login with invalid password
When I enter email "test@example.com"
And I enter password "wrongpassword"
And I click the "Sign In" button
Then I should see an error message "Invalid credentials"
@data-driven
Scenario Outline: Login validation
When I enter email "<email>"
And I enter password "<password>"
Then I should see "<result>"
Examples:
| email | password | result |
| test@example.com | ValidPass123 | dashboard |
| invalid | ValidPass123 | Invalid email format |
Robot Framework
.robot files structured with *** Settings ***, *** Variables ***, *** Test Cases ***, and *** Keywords *** sections. Variables use the ${NAME} syntax. Keywords follow the Given/When/Then BDD style.File extension: .robot
Copying and downloading results
After analysis completes, results appear in the output panel. You have two options for exporting:
- Copy to clipboard — click the copy icon on any output section to copy the full content to your clipboard
- Download — use the Download button to save the file with the correct extension for your chosen format
From the analysis history detail page, you can also download results as Markdown (.md) or raw JSON (.json) at any time.
Share links
You can generate a public URL to share an analysis with someone who doesn’t have an Orizon QA account.
Open the analysis
Go to History and click the analysis you want to share.
Open the Share dialog
Click the Share button in the top-right action bar.
Enable public sharing
Toggle Enable public sharing on. A shareable URL is generated immediately.
Copy the link
Click the copy icon next to the URL to copy it to your clipboard.
Anyone with the share link can view the analysis results. They cannot edit, re-run, or delete the analysis.
To revoke access, return to the Share dialog and toggle public sharing off.