Skip to content

Conversation

asirvadAbrahamVarghese
Copy link
Contributor

PR to include treeSelect API wait from selectAccordionItem command, which eliminates the need to handle this separately in every test.
This waits only when the request is actually triggered, since the treeSelect call may or may not fire if the node is already selected, as noted here

Based on what I’ve noticed the treeSelect POST API URL follows a common pattern across the app

  • /report/tree_select?id=xx-0_xx-0-0_rep-20&text=Account%2520Groups%2520-%2520Linux
  • /utilization/tree_select?id=mr-1&text=Region%25200
  • /catalog/tree_select?id=-Unassigned&text=Unassigned
  • /vm_or_template/tree_select?id=root&text=All%2520VMs%2520%2526amp%253B%2520Instances
  • /vm_cloud/tree_select?id=xx-arch&text=%2526lt%253BArchived%2526gt%253B
  • /vm_infra/tree_select?id=ms-107&text=Analysis%2520Failed
  • /storage/tree_select?id=ms-30&text=Store%2520Type%2520%252F%2520FCP
  • /pxe/tree_select?id=xx-xx-system&text=Examples%2520(read%2520only)
  • /miq_ae_class/tree_select?id=aen-1322&text=zxc
  • /ops/tree_select?id=z-2&text=%253Cstrong%253EZone%253A%2520Default%2520Zone%2520(current)%253C%252Fstrong%253E

which can be matched with /\/[^\/]+\/tree_select\?id=.*&text=.*/

@miq-bot assign @jrafanie
@miq-bot add-label cypress
@miq-bot add-label enhancement

Copy link
Member

@jrafanie jrafanie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. That URL pattern is pretty nasty due to inconsistency but at least it's only in 1 place now.

@jrafanie jrafanie merged commit bf47dcc into ManageIQ:master Sep 12, 2025
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants