@neighbouringRights
@contentNeighbouringRights
Feature: Neighbouring Upload

  Background: Clear browser
    Given I have a clear browser

  @id_41650844ab1777a4d880a43f8e4faa7947b381420a23e6e73d9ec1bea3b8f8c5
  Scenario: A neighbouring rights user can upload a valid CSV to S3
    Given a user from e2e_user for content
    When I log in to content silently
    And I can upload a valid CSV file
    And the valid file was successfully uploaded to s3

  @id_07ba7ded31afc04b4f57b48ee8da47f2f1b37e6489790fed1b172f50ede25d47
  Scenario: A neighbouring rights user can upload a invalid CSV to S3
    Given a user from e2e_user for content
    When I log in to content silently
    And I can upload a invalid CSV file
    And the invalid file was successfully uploaded to s3

  @id_cdcb701bbadfde9c579cdf76f115cadf1ea1a0676f2e1459b85346cd8e6b18f8
  Scenario: A neighbouring rights user cannot upload an incorrectly formatted CSV
    Given a user from e2e_user for content
    When I log in to content silently
    And I can upload a bad CSV file
    Then I get an error showing the file failed to upload