[MGNLTEST-297] Provide a Page Object for a "Banner" Created: 17/Aug/22  Updated: 21/Oct/22  Resolved: 21/Oct/22

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

Type: New Feature Priority: Neutral
Reporter: Christoph Meier Assignee: Harshini Pola
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1d 5.5h
Original Estimate: Not Specified

Attachments: PNG File Bildschirmfoto 2022-08-17 um 14.08.28.png     PNG File Bildschirmfoto 2022-08-17 um 14.08.46.png    
Template:
Acceptance criteria:
Empty

 Description   

So far we have "Alert" and "Notification" - which are both very similar - kind of "free floating bubbles" (with a messsage and possibly with buttons).

See screenshots for examples of banners.

Banners appear when sending message with the Messages app - or when an error occurs which is exposed at the UI. The later case is more important for UI tests.

Developer notes

The class should implement PageObject.
And it should override
void assertExists throws Throwable

AND ...
... as an exception it also would be nice to have a method
void assertDoesNotExists throws Throwable
While at first one may think that to check whether the PO does not exist, in a test we just could write:
!expect().banner().assertExists

BUT ... assertExists typically is implemented in a way that it returns very quickly, when the PO exists, but would wait looong if it does not exist.
Hence - !expect().banner().assertExists - would slow down such a test dramatically.



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

Let us ignore all notifications.

Reason: If we close one notifcation, it will close all possible stacked other notifications.

Comment by Christoph Meier [ 21/Oct/22 ]

reviewed & integrated

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