Feature: ContentPages

  @content_review
  @graphql_product
  @ows_track
  @id_a1464267688a02e1c04e5b9c0da48b43babe3e6119a12303903ecf78db2ec13d
  Scenario: Content has approval queue table with review button
    Given a user from test_user for content
    When I log in
    Then I am successfully logged in to content
    And I see review queue table
    And I see filters
    And I see review button

  @content_review
  @graphql_product
  @ows_track
  @id_63ded460a135433b296f116f353f1c7f4f4ba27acf4b09b3e7f41b4dcca8c06b
  Scenario: A content review user can see product metadata
    Given an orchard employee label_6971_admin for workstation
    And I have a new project and digital product for the user with label 6971 and artist 1684776
    And I upload artwork via api
    And I have a blank track with all required fields for label 6971
    And I upload a track via api
    When I validate and submit my product via api
    Then My product shouldn't be added to the legacy release approval queue
    And a user from test_user for content
    And I log in
    And I filter the review queue by product upc
    Then I can start a review of a product
    And I can see product review modal popup
    And I can see product notices
    And I can see product basics
    And I can see tracks
    And I can see contributors
    And I can see scheduling and pricing
    And I can skip a product during review

  @neighbouringRights
  @contentNeighbouringRights
  @id_9c197190f8d31eeee3430d6009859b149fa44ee62a5b327d89e8059446bc1f61
  Scenario: Validate that the content catalog page works
    Given a user from e2e_user visits content
    When I log in
    Then I can see that content-review my catalog page works