[MGNLTEST-87] Implement additional way to acquire instances of RenderedElement Created: 18/Aug/20  Updated: 09/Nov/23

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

Type: Improvement Priority: Neutral
Reporter: Michael Duerig Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: QA&Testing, ui-test-fwk
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: core-TF-features-bugs-improvements
Team: Foundation
Work Started:

 Description   

Currently the only way to acquire a RenderedPage.RenderedElement instance is by searching for text on a RenderedPage instance. I suggest to refine this mechanisms where it makes sense (i.e. try to identify other use cases):

  • acquire by other criteria (e.g. see org.openqa.selenium.By)
  • acquire a child from another RenderedElement


 Comments   
Comment by Michael Duerig [ 18/Aug/20 ]

/cc cmeier

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