Sha256: 7293825d2d43a9902204ca6d78033ff8f6ba4c70717dc98a3034225d93e2df5d
Contents?: true
Size: 1.27 KB
Versions: 2
Compression:
Stored size: 1.27 KB
Contents
@mobile @ios @android @regression Feature: Screen Navigation In order to ensure comprehensive support for native app navigation features As a developer of the TestCentricity gem I expect to validate that app screens can be accessed via navigation controls Background: Given I have launched the SauceLabs My Demo app And I am on the Products screen Scenario: Verify navigation menu can be invoked and is properly displayed When I open the navigation menu Then I expect the navigation menu to be correctly displayed When I close the navigation menu Then I expect the navigation menu to be hidden Scenario Outline: Verify screen navigation features When I tap the <screen_name> navigation menu item Then I expect the <screen_name> screen to be correctly displayed Examples: |screen_name | |About | |Login | |Webview | |SauceBot Video | Scenario Outline: Verify screen navigation features with popup modals When I tap the <screen_name> navigation menu item And I accept the popup request modal Then I expect the <screen_name> screen to be correctly displayed Examples: |screen_name | |QR Code Scanner | |Geo Location | |Biometrics |
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
testcentricity-3.0.4 | features/navigation.feature |
testcentricity-3.0.3 | features/navigation.feature |