Bug 2182667 - [WebUi] Provide description of structure of test marks in pcs-web-ui
Summary: [WebUi] Provide description of structure of test marks in pcs-web-ui
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pcs
Version: 9.1
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: 9.4
Assignee: Ivan Devat
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-29 09:45 UTC by Ivan Devat
Modified: 2023-08-15 07:12 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
This is an internal change aimed at making it easier to test pcs web UI. No doc update is needed.
Clone Of:
Environment:
Last Closed:
Type: Enhancement
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-6645 0 None None None 2023-04-19 22:20:59 UTC
Red Hat Issue Tracker RHELPLAN-153401 0 None None None 2023-03-29 09:46:56 UTC

Description Ivan Devat 2023-03-29 09:45:56 UTC
Provide description of structure of test marks in pcs-web-ui.

The description should be in document in json format. This document should be distributed as a part pcs-web-ui similarly to manifest.json. So, it would be possible to download this document from url similar to e.g. https://node:2224/ui/manifest-test-marks.json

The test marks are represented by attributes data-test of html elements of the page. Inside element marked like this can be nested html structure with another elements also marked by data-test. This way the marks creates tree-like structure.

In the mentioned json document, this structure should be represented by a json object. Keys of this object corresponds to the values of the top level data-test attributes and the values on the keys are objects (similar to top level object) representing the corresponding nested html structure.

Comment 1 Ivan Devat 2023-03-29 09:49:17 UTC
@nhostako @mmazoure Can we get a qa_ack+ for this issue? Thanks.


Note You need to log in before you can comment on or make changes to this bug.