Feature: Digital Audio Product Builder Basics

  # Recommend to delete — no need to test classical fields separately in E2E; unit/integration tests should cover this.
  @wip
  @ows_account
  @ows_project_manager
  @ows_artist
  @ows_marketing
  @frontend_distribution
  @ows_product_workflow
  @ows_product_digital
  @ows_product
  @graphql_product
  @ows_contracts
  @digital_product_builder_basics
  @id_649c8bdc716b637f98a6e43ab3a7f953fd452b3a0bf5dd9b4a0089cebd8608bc
  Scenario: Populate digital product 2 basics with required fields and classical fields
    Given an orchard employee label_7123 for workstation
    And I log in to workstation silently
    And I am on the digital product overview page for a newly-created product
    And I have classical data for digital product basics fields
    When I go to the digital product Basics section
    And I populate required digital product basics fields
    And I populate the digital product imprint with existing options
    And I populate the digital product basics classical fields
    And I submit the digital audio product basics page form
    And I go to the digital product Overview step
    Then I see the correct basics data on the digital product overview page
    # Project Manager I -> Create a new project as label with required fields and existing dropdowns
    When I am on the workstation catalog projects page
    Then I should see the project in the projects list


# Above is a consolidation of the following:
# cypress/e2e/workstation/productBuilder/digitalProductBuilderBasics.feature
# cypress/e2e/workstation/productBuilder/projectManagerI.feature -> Create a new project as label with required fields and existing dropdowns
# Pause pipeline execution while collecting data for framework comparison and refactor analysis