-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
[QE] Be able to add Techdocs Add-ons to Techdocs
-
False
-
-
False
-
-
Done
-
RHIDP-4713 - Be able to add Techdocs Add-ons to Techdocs
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
0% To Do, 0% In Progress, 100% Done
-
Release Note Not Required
-
-
EPIC Goal
Contribute QE automation for the Feature Be able to add Techdocs Add-ons to Techdocs.
Background/Feature Origin
Why is this important?
We need to be able to confidently say that the feature works as expected going forward. This can be achieved through the use or QE automation.
User Scenarios
- As an administrator, I want to be able to add Techdocs add-ons to RHDH
- As an administrator, I want to be able to remove Techdocs add-ons from RHDH
- As a user, I want to be able to see my documentation in RHDH with additional features provided by my administrator.
- As a developer, I want to understand how to create an add-on.
Dependencies (internal and external)
Acceptance Criteria
Release Enablement/Demo - Provide necessary release enablement details
and documents
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Playwright: <link or reference to playwright>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>
