# Refactored -> cypress/e2e/workstation/productBuilderMigration/physicalProductBuilderBasics.feature
Feature: Physical Product Builder Basics

  @refactor_old
  @ows_account
  @ows_product
  @graphql_product
  @ows_product_physical
  @ows_project_manager
  @ows_marketing
  @frontend_distribution
  @ows_product_configuration
  @id_fa46ce26214d70de3dc852fc059baa3e377d5ed84bb37a9159d35b8c54f033e0
  Scenario: Create physical product with release basics
    Given an orchard employee label_7123 for workstation
    And I log in to workstation silently
    And I have existing Physical Product data for label 7123 for all fields
    And I have a new project for a physical product
    When I add a product to the project
    And I select physical as the product type
    And I submit the physical audio product landing page form
    And I add release basics to the Physical Product
    And I go to the review section
    Then I see the correct physical release basics

  @refactor_old
  @ows_account
  @ows_product
  @graphql_product
  @ows_product_physical
  @ows_project_manager
  @ows_marketing
  @frontend_distribution
  @ows_product_configuration
  @id_4284b25592d6ab56c851850213ae77fbc96f61d0d600d477d68b4f0d468cd948
  Scenario: Create physical product with release basics and orchard generated UPC (PHYS-3636)
    Given an orchard employee label_7123 for workstation
    And I log in to workstation silently
    And I have existing Physical Product data for label 7123 for all fields
    And I have a new project for a physical product
    When I add a product to the project
    And I select physical as the product type
    And I submit the physical audio product landing page form
    And I add release basics to the Physical Product using an orchard generated UPC
    And I go to the review section
    Then I see the correct physical release basics with an orchard generated UPC

  # This scenario can be implemented as a frontend component test.
  @refactor_old
  @ows_product
  @graphql_product
  @ows_product_physical
  @frontend_distribution
  @id_4689a641d5538ca8768818922aa51538cc9ef0954f2d2c1365149287fcc8d8f8
  Scenario: Physical product validation
    Given an orchard employee label_7123 for workstation
    And I log in to workstation silently
    And I am on the project details page for the project: 3501773, product: 1916480
    When I add a product to the project
    And I select physical as the product type
    And I submit the physical audio product landing page form
    And I add empty release basics to the Physical Product
    Then I should see a validation error message on the physical product form

  # This scenario can be implemented as a frontend component test
  @refactor_old
  @ows_product
  @graphql_product
  @ows_product_physical
  @id_10d4bb903847d6fd5225338332c6c7cf2a4d7b4ca8fcba3ce9582f4238be9569
  Scenario: Physical product country of origin field is present and correct
    Given an orchard employee label_7123 for workstation
    And I log in to workstation silently
    And I am on the project details page for the project: 3501773, product: 1916480
    When I add a product to the project
    And I select physical as the product type
    When I submit the physical audio product landing page form
    Then The country of origin field should be present and usable