Adds SFRA 6.0

storefront-reference-architecture/test/acceptance/features/accountPage/addAddress.feature

@@ -0,0 +1,8 @@
+Feature: Add Address to User Account
+    As a shopper with an account, I want to be able to add a saved address
+
+@accountPage
+    Scenario: Shopper is able to add an address to their account
+        Given shopper logs into the website
+        And shopper clicks add new address
+        And shopper fills out address information

storefront-reference-architecture/test/acceptance/features/accountPage/addPayment.feature

@@ -0,0 +1,10 @@
+Feature: Add Payment to User Account
+    As a shopper with an account, I want to be able to add a saved payment
+
+@accountPage
+    Scenario: Shopper is able to add a payment to their account
+        Given shopper logs into the website
+        And shopper clicks add new payment
+        And shopper fills out their payment information
+        Then shopper clicks view payments
+        And shopper removes a saved credit card

storefront-reference-architecture/test/acceptance/features/accountPage/changePassword.feature

@@ -0,0 +1,8 @@
+Feature: Edit password of a User Account
+    As a shopper with an account, I want to be able to change my password
+
+@accountPage
+    Scenario: Shopper is able to change their password
+        Given shopper logs into the website
+        And shopper clicks edit password
+        And shopper changes their password

storefront-reference-architecture/test/acceptance/features/accountPage/editProfile.feature

@@ -0,0 +1,10 @@
+Feature: Edit profile of a User Account
+    As a shopper with an account, I want to be able to edit my profile
+
+    Background:
+        Given shopper logs into the website
+
+@accountPage @editProfile
+    Scenario: Shopper is able to edit their account information
+        Then shopper clicks edit profile
+        And shopper edits phone number

storefront-reference-architecture/test/acceptance/features/checkoutPage/editCart.feature

@@ -0,0 +1,15 @@
+Feature: Edit products within the cart
+    As a shopper I want to be able to add multiple products to my cart,
+    and edit my cart before entering checkout.
+
+@editCart
+    Scenario: Shopper is able to edit products in their cart
+        When shopper selects yes or no for tracking consent
+        Given Shopper searches for "Elbow Sleeve Ribbed Sweater"
+        Then selects size "S"
+        Then shopper changes product quantity
+        Then he adds the product to cart
+        Given Shopper searches for "Modern Striped Dress Shirt"
+        Then selects size "16R"
+        Then he adds the product to cart
+        Then shopper edits products in cart

storefront-reference-architecture/test/acceptance/features/homePage/addProductToCart.feature

@@ -0,0 +1,11 @@
+Feature: Add Product To Cart
+    As a shopper, I want to search for a product and add it to cart
+
+@homePage @cart
+    Scenario: Shopper is able to add a product to a cart
+        When shopper selects yes or no for tracking consent
+        Given Shopper searches for "Elbow Sleeve Ribbed Sweater"
+        Then selects size "S"
+        Then shopper changes product quantity
+        Then he adds the product to cart
+        Then he is able to see the correct product in cart

storefront-reference-architecture/test/acceptance/features/homePage/emailSignup.feature

@@ -0,0 +1,8 @@
+Feature: Email signup
+    As a shopper, I want to signup to mailing list
+
+@homePage
+    Scenario: Shopper is able to enter email for signup
+        When shopper selects yes or no for tracking consent
+        Then shopper enters email in signup form
+        And shopper subscribes to the email list

storefront-reference-architecture/test/acceptance/features/homePage/landHomePage.feature

@@ -0,0 +1,6 @@
+Feature: Land Home Page
+    As a shopper, I want to land on the home Page
+
+@homePage
+    Scenario: Shopper is able to land on the home Page
+        When shopper selects yes or no for tracking consent

storefront-reference-architecture/test/acceptance/features/homePage/locateStore.feature

@@ -0,0 +1,9 @@
+Feature: Store locator
+    As a shopper, I want to view available store locations
+
+@homePage
+    Scenario: Shopper is able to use store locator.
+        When shopper selects yes or no for tracking consent
+        Then shopper goes to store locator page
+        And shopper searches for a store
+        Then shopper searches for a store with different radius

storefront-reference-architecture/test/acceptance/features/homePage/verifyMiniCart.feature

@@ -0,0 +1,15 @@
+Feature: Modify & Verify Mini Cart
+    As a shopper, I want to verify selected product attributes and modify (edit quantity and remove product) mini cart
+
+@miniCart @miniCartGuestUser
+    Scenario: Shopper is able to modify mini cart, verify selected product attributes and goto Guest Checkout
+        Given shopper selects yes or no for tracking consent
+        When shopper is able to add and remove a product from minicart
+        And shopper is able to add a product and edit product quantity in minicart
+        Then shopper goes to Guest Checkout page from minicart
+
+@miniCart @miniCartRegisteredUser
+    Scenario: Shopper is able to modify mini cart, verify selected product attributes and goto Registered Checkout
+        Given shopper logs into the website
+        When shopper is able to add a product and edit product quantity in minicart
+        And shopper is able to navigate through minicart, registered checkout pages and remove the product from cart

storefront-reference-architecture/test/acceptance/features/loginPage/createAccount.feature

@@ -0,0 +1,18 @@
+Feature: Create an Account
+    As a shopper, I want to be able to create an account with the site
+
+@loginPage @createAccount @deepTest
+Scenario: Shopper is able to create a new account from the login page
+    Given shopper goes to the Login Page
+    Then shopper is able to click tab to create account
+    And shopper is able fill out registration information with new email
+    And shopper is able to click the create account button
+    And shopper does not see a username is invalid error
+
+@loginPage @createAccount
+Scenario: Shopper is not able to create an account that already exists
+    Given shopper goes to the Login Page
+    Then shopper is able to click tab to create account
+    And shopper is able fill out registration information with existing email
+    And shopper is able to click the create account button
+    And shopper sees a username is invalid error

storefront-reference-architecture/test/acceptance/features/loginPage/forgotPassword.feature

@@ -0,0 +1,12 @@
+Feature: Forgot Password
+    As a shopper, I want to be able to reset my password if I forgot my
+    login information
+
+@loginPage @forgotPassword 
+    Scenario: Shopper is able to reset their password
+        Given shopper goes to the Login Page
+        When shopper clicks forgot password
+        And shopper fills out their recovery email address
+        Then shopper should see request to change password prompt
+        # This is just half of the feature being tested with a dummy email
+        # Requires manual testing with a real email

storefront-reference-architecture/test/acceptance/features/loginPage/loginUser.feature

@@ -0,0 +1,14 @@
+Feature: User Login
+    As a shopper, I want to be able to log into the site
+
+@loginPage 
+    Scenario: Shopper is able to log into the site from the home page
+        Given shopper logs into the website
+
+@loginPage @mobile
+    Scenario: Shopper is able to log into the site mobile
+        Given shopper logs into the website on phone
+
+@loginPage @tablet
+    Scenario: Shopper is able to log into the site tablet
+        Given shopper logs into the website on tablet

storefront-reference-architecture/test/acceptance/features/pageDesigner/campaignBanner/campaignBanner.feature

@@ -0,0 +1,12 @@
+Feature: Campaign Banner on Page Designer Home Page
+    As a shopper, I shoiuld see the campaign banner
+
+@campaignBanner @pageDesigner
+    Scenario: Shopper should able to see the campaign banner
+        When shopper load Page Designer home page
+        Then shopper accept the Consent Tracking Modal
+        Then shopper should see the campaign banner
+        And shopper should see the campaign banner message
+        And shopper should see a close button on campaign banner
+        And shopper should be able to close the campaign banner
+        And shopper should no longer see the campaign banner

storefront-reference-architecture/test/acceptance/features/pageDesigner/carousel/carousel.feature

@@ -0,0 +1,24 @@
+Feature: Page Designer Carousel
+  As a shopper, I want to see the page designer carousel
+
+  @Carousel @pageDesigner
+  Scenario: Shopper is able to interact with the page designer carousel component
+    When shopper load Page Designer home page
+    Then shopper accept the Consent Tracking Modal
+    And Shopper sees the carousel "1"
+    Given Shopper sees carousel controls in carousel "1"
+    When Shopper clicks next in carousel "1" 1 time
+    Then Shopper should see the next slide in the first carousel
+    When Shopper clicks previous in carousel "1"
+    Then Shopper should see the previous slide in the first carousel
+  
+  @Carousel @pageDesigner
+  Scenario: Shopper is able to interact with the page designer carousel-2 component
+    When shopper load Page Designer home page
+    Then shopper accept the Consent Tracking Modal
+    And Shopper sees the carousel "2"
+    Given Shopper sees carousel controls in carousel "2"
+    When Shopper clicks next in carousel "2" 5 times
+    Then Shopper should see next product in the second carousel
+    When Shopper clicks previous in carousel "2"
+    Then Shopper should see previous slide in the second carousel

storefront-reference-architecture/test/acceptance/features/pageDesigner/category/category.feature

@@ -0,0 +1,9 @@
+Feature: category on Page Designer Home Page
+    As a shopper, I want to see the category component
+
+@category @pageDesigner
+    Scenario: Shopper is able to see the category
+        When shopper load Page Designer home page
+        Then shopper accept the Consent Tracking Modal
+        Then shopper should see the category components
+        And shopper can click on a category link

storefront-reference-architecture/test/acceptance/features/pageDesigner/imageAndText/imageAndText.feature

@@ -0,0 +1,10 @@
+Feature: Image And Text Component on Page Designer Home Page
+    As a shopper, I should see the Image And Text Component
+
+@ITC @pageDesigner
+    Scenario: Shopper should be able to see the Image And Text Component
+        When shopper load Page Designer home page
+        Then shopper accept the Consent Tracking Modal
+        Then shopper should see the image and text component
+        Then shopper should see the overlay message
+        Then shopper should go to new arrivals page clicking on the image

storefront-reference-architecture/test/acceptance/features/pageDesigner/mainBanner/mainBanner.feature

@@ -0,0 +1,10 @@
+Feature: Main Banner on Page Designer Home Page
+  As a shopper, I should see the main banner
+
+  @mainBanner @pageDesigner
+  Scenario: Shopper should able to see the main banner
+    When shopper load Page Designer home page
+    Then shopper accept the Consent Tracking Modal
+    Then shopper should see the main banner
+    Then shopper should see the main banner message
+    Then shopper should go to womens clothing dresses clicking on the main banner

storefront-reference-architecture/test/acceptance/features/pageDesigner/photoTile/photoTile.feature

@@ -0,0 +1,8 @@
+Feature: Photo Tile Component on Page Designer Home Page
+    As a shopper, I should see the Photo Tile Component
+
+@photoTile @pageDesigner
+    Scenario: Shopper should be able to see the Photo Tile Component
+        When shopper load Page Designer home page
+        Then shopper accept the Consent Tracking Modal
+        Then shopper should see the photo tile component

storefront-reference-architecture/test/acceptance/features/pageDesigner/popularCategory/popularCategory.feature

@@ -0,0 +1,10 @@
+Feature: Popular Category on Page Designer Home Page
+    As a shopper, I want to see the popular category component
+
+@popularCategory @pageDesigner
+    Scenario: Shopper is able to see the popular category
+        When shopper load Page Designer home page
+        Then shopper accept the Consent Tracking Modal
+        Then shopper should see the popularCategories layout
+        Then shopper should see the popularCategory components
+        And shopper can click on a popular category

storefront-reference-architecture/test/acceptance/features/pageDesigner/productTile/productTile.feature

@@ -0,0 +1,18 @@
+Feature: Product Tile on Page Designer Home Page
+    As a shopper, I should see the product Tile
+
+    @productTile @pageDesigner
+    Scenario: Shopper should able to see the product tile with default attributes
+        When shopper load Page Designer home page
+        Then shopper accept the Consent Tracking Modal
+        Then shopper should see the product tile component
+        Then shopper should see the alt attribute on product image
+        Then shopper should see the title attribute on product image
+        Then shopper should not see quickview on product tile
+        Then shopper should see the product name on product tile
+        Then shopper should see the regular price on product tile
+        Then shopper should see the strike-through price on product tile
+        Then shopper should see the sales price on product tile
+        Then shopper should go to the product details page clicking on the image
+        Then shopper load Page Designer home page
+        Then shopper should go to the product details page clicking on product name

storefront-reference-architecture/test/acceptance/features/pageDesigner/richText/richText.feature

@@ -0,0 +1,9 @@
+Feature: Rich Text Component on Page Designer Home Page
+    As a shopper, I should see the Rich Text Component
+
+@richText @pageDesigner
+    Scenario: Shopper should be able to see the rich text Component
+        When shopper load Page Designer home page
+        Then shopper accept the Consent Tracking Modal
+        Then shopper should see the rich text component
+        Then shopper should see the title

storefront-reference-architecture/test/acceptance/features/pageDesigner/shopCategory/shopCategory.feature

@@ -0,0 +1,11 @@
+Feature: Shop Category on Page Designer Home Page
+    As a shopper, I should see the Shop Category
+
+    @shopCategory @pageDesigner
+    Scenario: Shopper should able to see the Shop Category on Page Designer Home Page
+        When shopper load Page Designer home page
+        Then shopper accept the Consent Tracking Modal
+        Then shopper should see the shop category heading
+        Then shopper should see 5 shop categories
+        Then shopper should go to the category page by clicking on the category link
+

storefront-reference-architecture/test/acceptance/features/pageDesigner/shopTheLook/shopTheLook.feature

@@ -0,0 +1,10 @@
+Feature: Shop The Look Component on Page Designer Home Page
+    As a shopper, I should see the Shop The Look Component
+
+@shopTheLook @pageDesigner
+    Scenario: Shopper should be able to see the shop the look Component
+        When shopper load Page Designer home page
+        Then shopper accept the Consent Tracking Modal
+        Then shopper should see the shop the look component
+        Then shopper should see the title when hover over image
+        Then shopper should not see the setItem when hover over image on product

storefront-reference-architecture/test/acceptance/features/productDetailPage/pdpProductBackToPLP.feature

@@ -0,0 +1,11 @@
+Feature: Filter products from PDP
+    As a shopper I want navigate back to the previous plp using the back button.
+
+
+@productBackButton
+    Scenario: Shopper is able to go back to refined plp from pdp
+        When shopper selects yes or no for tracking consent
+        Given shopper searches for category from menu
+        And shopper clicks on the more button
+        Then Shopper clicks on the first product Tile
+        And Shopper clicks the back button on pdp

storefront-reference-architecture/test/acceptance/features/productDetailPage/pdpProductFilter.feature

@@ -0,0 +1,13 @@
+Feature: Filter products from PDP
+    As a shopper I want to be able to search for a product type
+    And then select different filter options to reduce the number of potential
+    items.
+
+@productFilter 
+    Scenario: Shopper is able to filter for products
+        When shopper selects yes or no for tracking consent
+        Given shopper searches for category from menu
+        And shopper filters product by color
+        And shopper filters product by size
+        And shopper filters product by price
+        And shopper filters product by option

storefront-reference-architecture/test/acceptance/features/productDetailPage/pdpQuickViewSearch.feature

@@ -0,0 +1,9 @@
+Feature: Product Quickview
+    As a shopper I want to be able to search for a product from the menu
+    then add the product to cart using Quick View
+
+@productQuickView 
+    Scenario: Shopper is able to shop using a product's quick view
+        When shopper selects yes or no for tracking consent
+        And shopper opens product quick view from home page
+        Then shopper adds to cart from Quick View

storefront-reference-architecture/test/acceptance/features/productDetailPage/pdpSimpleLayout.feature

@@ -0,0 +1,25 @@
+Feature: Product Detail Page Simple Layout
+    As a shopper, I want to see Product Details for a Simple Product
+
+    Background: shoper is on product details page
+        When shopper goes to the Product Detail Page
+
+    @simpleProductDetail
+    Scenario: Shopper sees all the product related information on the Simple product page
+        Then shopper sees all the product related information
+
+    @simpleProductDetail_breadcrumbs
+    Scenario: Shopper sees the correct breadcrumbs and is on right navigation path
+        Then shopper sees the correct breadcrumbs
+
+    @simpleProductDetail_socialLinks
+    Scenario: Shopper sees the correct social links
+        Then shopper sees the correct social links
+    
+    @simpleProductDetail_addToCartButton
+    Scenario: Shopper sees the Add to Cart Button Enabled
+        Then shopper is able to see Add to Cart Button Enabled
+    
+    @simpleProductDetail_addToCartButton
+    Scenario: Shopper is able to copy Product URL using Copy Link Icon
+        Then shopper is able to copy Product URL using Copy Link Icon

storefront-reference-architecture/test/acceptance/features/sourceCodeRedirects/categoryRedirect.feature

@@ -0,0 +1,8 @@
+Feature: Use a source code to land on a category page
+    As a shopper I want to be able land on a category landing page using a sourcecode link
+
+
+@sourceCodeRedirect
+    Scenario: Use a source code to land on a category page
+        Then shopper lands on the expected category landing page
+        And shopper sees all the category landing page related information

storefront-reference-architecture/test/acceptance/features/sourceCodeRedirects/pageRedirect.feature

@@ -0,0 +1,8 @@
+Feature: Use a source code to land on a content page
+    As a shopper I want to be able land on a content page using a sourcecode link
+
+
+@sourceCodeRedirect
+    Scenario: Shopper uses the src code to go to a content page
+        Then shopper lands on the expected content page
+        And shopper sees the expected content page

storefront-reference-architecture/test/acceptance/features/sourceCodeRedirects/pdpRedirect.feature

@@ -0,0 +1,8 @@
+Feature: Use a source code to land on a pdp page
+    As a shopper I want to be able land on a pdp page using a sourcecode link
+
+
+@sourceCodeRedirect
+    Scenario: Shopper uses the src code to go to a pdp
+        Then shopper lands on the expected pdp
+        And shopper sees all the product related information v2

storefront-reference-architecture/test/acceptance/features/testSuites/happyPath-guest.feature

@@ -0,0 +1,19 @@
+Feature: Follow the happy path of a guest user
+    As a shopper, I want to shop for a product and fill out the correct
+    shipping information/billing information in checkout.
+
+@happyPath
+    Scenario: Guest shopper should be able to follow the checkout flow
+        When shopper selects yes or no for tracking consent
+        Given Shopper searches for "Elbow Sleeve Ribbed Sweater"
+        Then selects size "S"
+        Then he adds the product to cart
+        Then shopper goes to cart
+        Then shopper changes product quantity to "2"
+        And shopper selects checkout from cart
+        And shopper selects checkout as guest
+        And shopper fills out shipping information
+        Then shopper proceeds to payment section
+        And shopper fills out billing information
+        Then shopper places order
+        And shopper verifies the order confirmation page

storefront-reference-architecture/test/acceptance/features/testSuites/happyPath-registered.feature

@@ -0,0 +1,28 @@
+Feature: Follow the happy path of a registered user
+    As a shopper, I want to shop for a product, log into my account, and fill out the correct
+    shipping information based on previous saved user data.
+
+    Background:
+        Given shopper logs into the website
+        And shopper clicks add new payment
+        And shopper fills out their payment information
+
+@happyPath @testing
+    Scenario: Registered shopper should be able to follow the checkout flow
+        Given Shopper searches for "Elbow Sleeve Ribbed Sweater"
+        Then selects size "S"
+        Then he adds the product to cart
+        Then shopper goes to cart
+        Then shopper changes product quantity to "2"
+        And shopper selects checkout from cart
+        And shopper verifies shipping information
+        Then shopper proceeds to payment section
+        And shopper fills out registered user billing information
+        Then shopper places order
+        And shopper verifies the order confirmation page
+        Then shopper goes to profile saved payments page and deletes credit card
+        And logs out of the account
+        Given shopper goes to the Login Page
+        Then shopper is able to fill out the order number, email, and zip code
+        And shopper is able to click the check status button
+        And shopper is able to view order detail