[MGNLTEST-265] Provide Page Object for Banner messages Created: 14/Jun/22  Updated: 03/Oct/22  Resolved: 03/Oct/22

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

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

Attachments: PNG File Bildschirmfoto 2022-06-13 um 10.54.21.png     PNG File Bildschirmfoto 2022-06-13 um 10.55.30.png     PNG File Bildschirmfoto 2022-06-13 um 10.56.39.png    
Template:
Acceptance criteria:
[ ]* Implement the new PO
[ ]* Provide self-tests
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)

 Description   

Provide a page object for "banner messages".

Possible API(s)

New PO BannerMessage

  • String getTitle
  • String getMessage
  • BannerMessage.Type getType
  • void clickReadMore
  • void clickReadAllNotifications
  • void close

New methods on PageObjects to access or check for possible banner message.

  • boolean hasBanner
    • whether the UI contains a banner (or stacked banners)
  • Optional <BannerMessage> getBanner
    • returns the banner message currently sticked on the UI (the one on top)

The UI can indicate whether there are actually "multiple" banner - but the only way it does this is by showing an additional button ("Read all notifications"). Hence I propose that we mainly ignore the multiple banner thingy.



 Comments   
Comment by Christoph Meier [ 03/Oct/22 ]

This one id "duplicated" by MGNLTEST-297

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