[MGNLTEST-421] Improve ContentApp#selectRowByPath(absolutePath) Created: 03/Jul/23  Updated: 16/Oct/23  Resolved: 05/Sep/23

Status: Closed
Project: Magnolia Test Framework
Component/s: None
Affects Version/s: None
Fix Version/s: 1.4.6

Type: Improvement Priority: Neutral
Reporter: Christoph Meier Assignee: Harshini Pola
Resolution: Resolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Improve-ContentApp-API
Work Started:

 Description   

ContentApp#selectRowByPath is somehow erratic.


In tree-view:

Imagine this example content:

/root-item
  /level1-item
    /level2-item

If the tree is fully collapsed,
Then selecting contentApp#selectRowByPath("root-item/level1-item")
-> Works fine

If the item "root-item" is selected
Then selecting contentApp#selectRowByPath("root-item/level1-item")
-> fails
Instead
to select level1-item - it requires this call:
contentApp#selectRowByPath("level1-item")

P.S. Leading slash can be added or omitted, doesn't matter.

This behaviour is a bit weird, unanticipated.
A typical test / scenario workflow contains subsequent actions with multiple selections ... and the required code to select becomes a bit weird.

The method #selectRowByPath should always work "the same", where the parameter always should be the "path" - independent from what had been selected upfront.

In case we implement ContentApp#unselectAndReset - #selectRowByPath could call #unselectAndReset internally upfront, which may fix the problem.


In list-view

seems like that doesn't work at all when using "root-item/level1-item" or "/root-item/level1-item" as parameter ... be be checked again.



 Comments   
Comment by Harshini Pola [ 05/Sep/23 ]

Updated, reviewed and merged

Generated at Mon Feb 12 07:48:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.