Workspace / Overview
DEMO ENVIRONMENT
RK
RELEASE QUALITY CONTROL

Testing overview

From product requirements to release-ready evidence — in one workflow.

✦
Agent is ready to review a release

Latest sample release Fleet Gateway 4.8.2 has source changes analyzed and 12 draft test cases generated.

Tracked releases◷
08
Across 3 projects
Test cases generated☷
124
↑ 18%vs previous release
Latest sanity pass rate✓
92.4%
Fleet Gateway 4.8.1
Open linked bugs⚑
07
2 high priority· Jira linked

Release pipeline

Track each release from discovery to report

FG
Fleet Gateway 4.8.2FLEET · Release candidate · Updated 14 min ago
Needs approval8 / 12 steps
TC
Telematics Core 2.6.0DEVICE · Release candidate · Updated yesterday
Passed10 / 10 steps
PT
Portal UI 1.19.0PORTAL · In analysis · Updated 2 days ago
Analyzing3 / 11 steps

Agent activity

Recent workflow events

LIVE DEMO
✓
Source diff analyzed

12 files changed · 4 modules detected

14 min ago
✦
Test cases generated

12 drafts from 6 Jira stories

16 min ago
↗
Confluence requirements synced

3 pages · 9 requirement statements

19 min ago
⚑
Potential regression detected

Retry handling may affect reconnect flow

22 min ago

Release workflow

Human approval stays in control before any test execution.

✓DiscoverConfluence + Jira
✓AnalyzeRelease notes + Git diff
3ReviewApprove test plan
4ExecuteSanity suite
5ReportResults + Jira bugs
RELEASE MANAGEMENT

Release pipeline

Inspect source changes, trace requirements, and approve test plans.

⌕
RELEASESOURCE / VERSIONTEST CASESSTATUSUPDATED
SELECTED RELEASE

Fleet Gateway 4.8.2

Release candidate · FLEET project

Needs approval
HUMAN-IN-THE-LOOP

Test case review

Review, edit, and approve AI-generated tests before execution.

✦
12 test cases generated for Fleet Gateway 4.8.2

Generated from Confluence requirements, Jira stories, release notes and the Git diff. Review all assumptions before execution.

⌕
12 test cases
ID / TEST CASETYPEPRIORITYTRACEABILITYSTATUS
ⓘ Approval is required before the agent can run the test suite. Demo execution simulates results and does not connect to a real environment.
EXECUTION EVIDENCE

Test runs

Sanity execution results, environment details, and evidence.

✓
Latest demo run · Telematics Core 2.6.0

10 tests executed · 9 passed · 1 failed · Completed 28 Oct 2026, 10:42 IST.

Executed▷
10
Latest run
Passed✓
9
90% pass rate
Failed×
1
Review required
Linked bugs⚑
2
Jira demo records

Execution history

Simulated results for demonstration

DEFECT TRACEABILITY

Jira bugs

Failures and potential defects linked back to tests, requirements, and releases.

ISSUESUMMARYSEVERITYLINKED TESTRELEASESTATUS
In connected mode, the agent should create Jira issues only after user confirmation and store the returned issue key.
CONNECT YOUR TOOLCHAIN

Integrations

Connect your own Confluence, Jira, and Git repositories after the POC review.

Demo mode
Not connected

Confluence

Fetch requirement pages, acceptance criteria, architecture notes, and release documentation.

Not connected

Jira

Map requirements to issues, read release tickets, and link discovered defects to failed tests.

Not connected

Git provider

Read tags, release branches, changelogs, commit diffs, and changed files for the target version.

Not connected

Test runner

Connect a controlled test environment or CI runner to execute approved sanity tests and collect logs.

ⓘ
Security note

This POC is frontend-only. Do not enter real API tokens here. Production credentials must be stored in a backend secret manager, never in browser code.

GUARDRAILS & POLICY

Agent settings

Configure how the testing agent should reason and what it is allowed to do.

Execution policy

Test generation preferences