Sha256: 5ee7c3b02b4887f48bb617b5588372ca89fc1ede0f82b9c9e7ca5cd6b49bfca7

Contents?: true

Size: 951 Bytes

Versions: 3

Compression:

Stored size: 951 Bytes

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 |

Version data entries

3 entries across 3 versions & 1 rubygems

Version Path
testcentricity-3.0.2 features/navigation.feature
testcentricity-3.0.1 features/navigation.feature
testcentricity-3.0.0 features/navigation.feature