XML

Word

Printable

Epic Name:
cnv-testing
Story Points:
77
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Acceptance Criteria:
Hide

No docs

No UXD

No QE

Review portions of our docs/features using an AI agent and open bugs for any detected issues

Set of screenshot-based demos showing prompts and the results

Report about the success rate and proposed next steps
Show
No docs No UXD No QE Review portions of our docs/features using an AI agent and open bugs for any detected issues Set of screenshot-based demos showing prompts and the results Report about the success rate and proposed next steps
Component Fix Version(s):
None
Epic Status:
To Do
Hierarchy Progress Bar:

100% To Do, 0% In Progress, 0% Done

Goal

Detect discrepancies and gaps in our documentation by using an AI agent.

User Stories

High-Level goal-based user story, with context.
"As a <VM owner/cluster administrator>, I want <to Achieve Some Goal>, so that <Some Reason/Context>."
another user story

<List of things not included in this epic, to alleviate any doubt raised during the grooming process.>

We should experiment with LLMs as the "user" running these scenarios
It could read from the docs
It would be prompted to use the system
cnv2 or bleeding.cnv can be used for this testing
The behavior should approximate a real user, with long running VMs etc.
The test is restrained as anybody else on these cluster, additional resources (VLAN) should be requested from the cluster admin

1.	upstream roadmap issue	New	Unassigned
2.	upstream design	New	Unassigned
3.	upstream documentation	New	Unassigned
4.	upgrade consideration	New	Unassigned
5.	test plans in polarion	New	Unassigned
6.	automated tests	New	Unassigned
7.	downstream documentation merged	New	Unassigned
8.	CNV QE DevOps Requirement/Enablement	New	Unassigned