Sha256: 556edae8694dce091a39b07f2342a029ee5f28f4637d49e1f5662b7d79572c7a

Contents?: true

Size: 848 Bytes

Versions: 4

Compression:

Stored size: 848 Bytes

Contents

@mobile @ios @android @regression


Feature:  App screen deep links
  In order to ensure comprehensive support for native app deep links
  As a developer of the TestCentricity gem
  I expect to validate that app screens can be directly accessed with minimal UI interactions


  Background:
    Given I have launched the SauceLabs My Demo app


  Scenario Outline:  Verify screens can be directly accessed via deep links
    Given I am on the <start> screen
    When I load the <destination> screen
    Then I expect the <destination> screen to be correctly displayed

    Examples:
      |start    |destination        |
      |Products |About              |
      |Products |Login              |
      |Products |Webview            |
      |Products |Checkout - Address |
      |Products |Checkout - Payment |
      |About    |Products           |

Version data entries

4 entries across 4 versions & 1 rubygems

Version Path
testcentricity-3.0.3 features/deep_links.feature
testcentricity-3.0.2 features/deep_links.feature
testcentricity-3.0.1 features/deep_links.feature
testcentricity-3.0.0 features/deep_links.feature