You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two of the e2e tests of two-up view on mobile are for the time being ignored because we didn't have a way to get to page 2 on mobile. Maybe we could use access keys to go to page 2 on mobile?
What is the expected behavior?
These tests should not be ignored.
What is the current behavior?
These two tests are ignored:
@ignore @android@iphone
Scenario: Two-Up pages mobile
Given the viewer is opened with a publication with viewing hint "paged"
And the user is on page 2
Then only page 2 is displayed
@ignore @android@iphone
Scenario: User select Two-Up mode
Given the viewer is opened with a publication with viewing hint "paged"
And the layout is two-page
And the user is on page 2
Then page 2 and 3 are displayed
What is the use-case or motivation for changing an existing behavior?
Better test suit
Which versions of Angular, OS, TypeScript, browsers are affected?
Android and iPhone
The text was updated successfully, but these errors were encountered:
Bug, feature request, or proposal:
Two of the e2e tests of two-up view on mobile are for the time being ignored because we didn't have a way to get to page 2 on mobile. Maybe we could use access keys to go to page 2 on mobile?
What is the expected behavior?
These tests should not be ignored.
What is the current behavior?
These two tests are ignored:
@ignore
@android @iphone
Scenario: Two-Up pages mobile
Given the viewer is opened with a publication with viewing hint "paged"
And the user is on page 2
Then only page 2 is displayed
@ignore
@android @iphone
Scenario: User select Two-Up mode
Given the viewer is opened with a publication with viewing hint "paged"
And the layout is two-page
And the user is on page 2
Then page 2 and 3 are displayed
What is the use-case or motivation for changing an existing behavior?
Better test suit
Which versions of Angular, OS, TypeScript, browsers are affected?
Android and iPhone
The text was updated successfully, but these errors were encountered: