Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Testing Flows

Table of Contents
minLevel1
maxLevel7
outlinetrue
separatorpipe

Testing Support

1- Useful links & tips

2- Documentation

https://luminoslabs.atlassian.net/wiki/spaces/HC/pages/3718774833

https://luminoslabs.atlassian.net/wiki/spaces/HC/pages/3745611791

3- Notes

  • [CMS] Hawksearch does not differentiate between pages (content) and products (product) in the dashboard and that is why a CMS page shows up under “Top Product Match” when searching for it in Hawksearch dashboard.

Connector: Variant attributes roll-up indexing (default)

By Default only Index parents with children attributes rolled up into the parent (Standard Way). This should be how the connector is setup when initially installed

Note

Notes on Foundation:

  1. Following variant fields are NOT indexed or rolled up into the parent(product/bundle/package) as part of this approach:

    1. Child_Color, Child_Size, Child_DisplayName, Child_Code, Child_Url

    2. Inventory_{WarehouseCode} , Price_{MarketId}_{Currency}

  2. For Bundles and Packages only Variant entries(components) are indexed, anything else is NOT.

  3. Inventory_{WarehouseCode} , Price_{MarketId}_{Currency} are indexed only for Packages.

  4. ImageAlt, ImageURL are indexed only for products in foundation.

Opti setup: most common

Expand
title1 website (2 pagetypes: standard, location item) | 1 catalog: multi-language & multi-market | products-variants | bundle-variants | packages-variants | categories

Scenario(s) + steps

Full Indexing Status

Incremental Indexing Status

Notes

1

Manual/Scheduled Run

Manual/Scheduled Run

2

https://techromix.atlassian.net/browse/HC-44

Fields to check: SiteId | MetaTitle | Keywords | BackgroundImage | MainBody | Coordinates | Id | Name | StartPublish | StopPublish | IndexedOn | ContentLink | ParentLink | ItemType | Url |

Id = ContentLink for the CMS pages

3

CMS - Standard & Location Item page types are indexed

  • Create a Standard page & a Location Item page → run the indexing job → verify that page and its fields is available in Hawksearch

  • Update the page → run the indexing job → verify updates are available in Hawksearch

  • Delete the page → run the indexing job → verify it is deleted in Hawksearch (question)

  •  Pass
  •  Fail
  •  Pass
  •  Fail

4

CMS - Other page types are NOT indexed

  • Create a Blog Item page & a Two Column Landing Page → run the indexing job → verify it is NOT available in Hawksearch

  •  Pass
  •  Fail
  •  Pass
  •  Fail

5

NO CMS - Catalog only setup

  • Verify that no CMS changes to Standard or Location Item page types (create, update, delete) are indexed

  •  Pass
  •  Fail
  •  Pass
  •  Fail

6

https://techromix.atlassian.net/browse/HC-23

7

Verify that the Category structure is sent to Hawksearch

  •  Pass
  •  Fail
  •  Pass
  •  Fail
Tip

API issue on Opti side - fixed on Men’s category is not displayed in the side-bar for filtering. We are waiting for a reply from Jonathan.

8

Edit the Category structure and verify it is updated in Hawksearch

  •  Pass
  •  Fail
  •  Pass
  •  Fail

9

Delete categories and verify in Hawksearch that:

  • the category is not available

  • the products under that category are not available

  •  Pass
  •  Fail
  •  Pass
  •  Fail

10

Product-variant catalog structure

  • only variant color is rolled up as a list under the Product

  • variants are not sent separately

  • no other info from variant is sent, this will be custom made on the projects it is used

  •  Pass
  •  Fail
  •  Pass
  •  Fail

11

Variant-only catalog structure

  • not supported with this type of indexing

  •  Pass
  •  Fail
  •  Pass
  •  Fail
Info

Categories with only variants underneath are not sent to Hawksearch.

12

Products - Fields to check

  • from product:ID | Name | StartPublish | StopPublish | IndexedOn | ContentLink | ParentLink | ItemType | URL | Code | Category |CatalogId| DisplayName | Markets | Manufacturer | Model | ModelYear | Warranty | Brand | Department | OnSale | NewArrival | ProductStatus | Description | LongDescription | ImageUrl | ImageAlt

  • rolled up from variant: Size | Color | Sku | Mpn | Upc | Description

13

Verify that product fields are sent to Hawksearch for each product

  •  Pass
  •  Fail
  •  Pass
  •  Fail
Tip

→ fixed on DEV by Hawksearch team on

Size for product variants is indexed and displayed as facet BUT not when you click on Boost->Explain - see following test product: “ASHBURY DRESS”

14

Edit product information and verify that updates are sent to Hawksearch

  • Images and other digital assets will be indexed as part of a product

  •  Pass
  •  Fail
  •  Pass
  •  Fail

15

Delete product information and verify that it is also removed in Hawksearch

  •  Pass
  •  Fail
  •  Pass
  •  Fail

16

Update Parent of product and verify the Category ID and Parent link is updated

Test data/Input

  • CatALevel1 (under catalog) - 1073741845

    • CatALevel2 - 1073741846

      • CatALevel3 - 1073741847

  • CatBLevel1 - 1073741848

    • CatBLevel2 - 1073741850

  • Initial Parent: CatALevel3

  • New Parent: CatBLevel2

  •  Pass
  •  Fail
  •  Pass
  •  Fail

Noemi Racz (Unlicensed) we need to re-test all category related scenarios due to to the change made to display all categories in the tree

17

Product belongs to several categories

  • Parent link is displayed for main the primary category

  • Category ID is sent for all the categories the product belongs to

  •  Pass
  •  Fail
  •  Pass
  •  Fail

18

Product belongs to several categories

  • delete one secondary category and verify the Category link is removed from the product in Hawksearch

  •  Pass
  •  Fail
  •  Pass
  •  Fail

19

Delete a product’s Primary category

Input (tip: backup & restore DB)

  • prod#1 (Primary category only): LL SAMMY SHIRT

  • prod#2 (Primary and secondary categories): LUCIEN COTTON TWILL COAT

Output:

for product#1(under Primary category only):

  •  Optimizely → category is deleted, product is moved under catalog
  •  Hawksearch → product is no longer displayed

for product#2(under Primary and secondary categories):

  •  Optimizely → product is moved under catalog root and has primary category empty
  •  Hawksearch → product is displayed with following updates:
    •  the category vanishes from Dashboard/ does not appear in search results
    •  Category ID is updated and contains all the secondary categories linked to the product in Optimizely
    •  ParentLink is updated to Catalog ID
    •  URL is updated with CatalogID as product’s parent
  •  Pass
  •  Fail
  •  Pass
  •  Fail

20

Delete product and verify the product is removed in Hawksearch

Test data:

  • LL POE CROPPED JERSEY PANT

  •  Pass
  •  Fail
  •  Pass
  •  Fail

21

https://techromix.atlassian.net/browse/HC-32 | https://techromix.atlassian.net/browse/HC-34

Bundles - Fields to check:

  • from bundle: ID | Name | StartPublish | StopPublish | IndexedOn | ContentLink | ParentLink | ItemType | URL | Code | Category | CatalogId | DisplayName | Markets

  • rolled up from variant: Size | Color | Description (*only variants are considered children)

22

Bundle level information is sent to Hawksearch

Input/Test data:

  • bundle#1 (with variants): “LL Bundle 2Variants”

  • bundle#2 (with products ): “LL Bundle Linked”

  • bundle#3 (with variants ): “LL Bundle 1Variant"

Output:

  •  bundle fields are indexed for all bundles (see fields to check)
  •  variant fields are rolled up for bundle with variants (see fields to check)
  •  edit bundle#1 information → updated fields are indexed (Images and other digital assets will be indexed as part of a product or variant)
  •  delete bundle #3 information → deleted information is no longer displayed in Hawksearch
  •  Pass
  •  Fail
  •  Pass
  •  Fail
Note

ImageAlt, ImageURL are not indexed and displayed in Hawksearch - per LL Dev team: ImageAlt, ImageURL will be indexed only for products in foundation

23

Update Parent of a bundle and verify the Category ID and Parent link is updated

Test data/Input

  • CatALevel1 (under catalog) - 1073741845

    • CatALevel2 - 1073741846

      • CatALevel3 - 1073741847

  • CatBLevel1 - 1073741848

    • CatBLevel2 - 1073741850

  • Initial Parent: CatALevel3

  • New Parent: CatBLevel2

  •  Pass
  •  Fail
  •  Pass
  •  Fail

24

Bundle belongs to several categories

Test data:

  • bundle#1 - “LL Bundle 3Variants”:

    • primary category: 1073741841 (LL Misc)

    • secondary categories: 1073741839(Sweaters), 1073741840(LL_Jackets)

    • delete: 1073741839(Sweaters)

  • bundle#2 - “LL Bundle Linked” :

    • primary category: 1073741841 (LL Misc)

    • secondary categories: 1073741839(Sweaters), 1073741837(LL Shoes)

    • update primary category to: 1073741840(LL_Jackets) and vice-versa for incremental

Output:

  •  verify Parent link and Category ID fields in Hawksearch for bundle#1 & 2→ Parent link is displayed for the primary category & Category ID is sent for all the categories the bundle belongs to
  •  delete one secondary category for bundle #1→ verify the Category link is removed from the bundle in Hawksearch
  •  update bundle#2 Primary category → verify the ParentLink is updated in Hawksearch
  •  Pass
  •  Fail
  •  Pass
  •  Fail

25

Delete a Bundle’s Primary category

Input:

  • bundle#1 (Primary category only): LL Bundle Primary2delete

  • bundle#2 (Primary and secondary categories): LL Bundle 2delete2

Output:

bundle#1(under Primary category only):

  •  Optimizely → bundle is moved under catalog, category is deleted
  •  Hawksearch → bundle is no longer displayed on Dashboard/in search results

bundle#2(under Primary and secondary categories):

  •  Optimizely → bundle is moved under catalog root
  •  Hawksearch → bundle is displayed with following updates:
    •  category vanishes from Dashboard/ does not appear in search results
    •  Category ID is updated and contains all the secondary categories linked to the product in Optimizely
    •  ParentLink is updated to Catalog ID
    •  URL is updated with CatalogID
  •  Pass
  •  Fail
  •  Pass
  •  Fail

26

Delete bundle and verify the bundle is removed in Hawksearch

Test data:

  • LL Bundle Secondary2delete

  •  Pass
  •  Fail
  •  Pass
  •  Fail

27

https://techromix.atlassian.net/browse/HC-33 | https://techromix.atlassian.net/browse/HC-35

Packages - Fields to check:

  • from package: ID | Name | StartPublish | StopPublish | IndexedOn | ContentLink | ParentLink | ItemType | URL | Code | Category | CatalogId | DisplayName | Markets | Inventory_{WarehouseCode} | Price_{MarketId}_{Currency}

  • rolled up from variants under Package entries: Size | Color | Sku | Mpn | Upc | Description

*only variants are considered children

28

Package level information is sent to Hawksearch

Input/Test data:

  • package#1 (with variants): “LL Package 2Variants”

  • package#2 (with packages): “LL Package SingleMarket”

  • package#3 (with variants): “LL Package 2Delete2”

Output:

  •  package fields are indexed (see fields to check)
  •  variant fields are rolled up for package #2 (see fields to check)
  •  edit package#1 information → updated fields are indexed (Images and other digital assets will be indexed as part of a product or variant)
  •  delete package #3 information → deleted information is no longer displayed in Hawksearch
  •  Pass
  •  Fail
  •  Pass
  •  Fail
Tip

→ fixed on DEV by Hawksearch team on

  • Size for variants added under Package entries is indexed and displayed as facet BUT not when you click on Boost->Explain - see following test packages: “LL Package 2Delete1” and “LL Package 2Variants”

Note

ImageAlt, ImageURL are not indexed and displayed in Hawksearch - per LL Dev team: ImageAlt, ImageURL will be indexed only for products in foundation

29

Update Parent of a package (kit) and verify the Category ID and Parent link is updated

Test data/Input

  • CatALevel1 (under catalog) - 1073741845

    • CatALevel2 - 1073741846

      • CatALevel3 - 1073741847

  • CatBLevel1 - 1073741848

    • CatBLevel2 - 1073741850

  • Initial Parent: CatALevel3

  • New Parent: CatBLevel2

  •  Pass
  •  Fail
  •  Pass
  •  Fail

30

Package (kit) belongs to several categories

Test data:

  • package#1 - “LL Package Canada” has:

    • primary category: 1073741841 (LL Misc)

    • secondary categories where it’s linked: 1073741839(Sweaters), 1073741840(LL_Jackets)

    • delete: 1073741839(Sweaters)

  • package#2 - “LL Package Spain” has:

    • primary category: 1073741840(LL_Jackets)

    • secondary categories: 1073741841 (LL Misc), 1073741839(Sweaters)

    • update primary category to: 1073741837 (LL Shoes)

Output:

  •  verify Parent link and Category ID fields in Hawk for package#1 & 2→ Parent link is displayed for the primary category & Category ID is sent for all the categories the package (kit) belongs to
  •  delete one secondary category for package #1→ verify the Category link is removed from the package (kit) in Hawksearch
  •  update package#2 Primary category for → verify the ParentLink is updated in Hawksearch
  •  Pass
  •  Fail
  •  Pass
  •  Fail

31

Delete a package (kit)’s Primary category

Input(tip for testing: backup & restore DB):

  • package#1 (Primary category only): LL Package 2Delete3

  • package#2 (Primary and secondary categories): LL Package 2Delete5

Output:

package#1(under Primary category only):

  •  Optimizely → Category is deleted, package is moved under the Catalog
  •  Hawksearch → package is no longer displayed on Dashboard/in search results

package#2(under Primary and secondary categories):

  •  Optimizely → package is moved under catalog root
  •  Hawksearch → package is displayed with following updates:
    •  category vanishes from Dashboard/ does not appear in search results
    •  Category ID is updated and contains all the secondary categories linked to the product in Optimizely
    •  ParentLink is updated to Catalog ID
    •  URL is updated with CatalogID as the package’s parent
  •  Pass
  •  Fail
  •  Pass
  •  Fail

Test result:

For package with Primary & Secondary categories, when primary cat is deleted, the following information is indexed in Hawksearch:

32

Delete package (kit) and verify the package (kit) is removed in Hawksearch

Test data:

  • package with variants: LL Package 2Delete1

  •  Pass
  •  Fail
  •  Pass
  •  Fail

33

https://techromix.atlassian.net/browse/HC-38 | https://techromix.atlassian.net/browse/HC-39

34

Product published on multiple markets in Optimizely

Input:

  • all products have markets: Australia, Canada, Spain, UK, USA

    • Product#1 - LL JADE HIGH BOOT

    • Product#2 - TRINITY STRAPPY MID SANDAL

    • Product#3 - KARLIE TROUSER

Tests & Output:

  •  Verify the list of markets is sent to Hawksearch on product level(for any product)
  •  Inactivate UK market from product #2 → only Australia, Canada, Spain, USA markets are displayed
  •  Activate Sweden market for product#3 → Australia, Canada, Spain, UK, USA & Sweden markets are displayed in Hawksearch
  •  Pass
  •  Fail
  •  Pass
  •  Fail

35

Bundle published on multiple markets in Optimizely

Input:

  • all bundles start with markets: Australia, Canada, Spain, UK, USA

    • Bundle#1 - LL Bundle 2delete2

    • Bundle#2 - LL Bundle 3Variants

    • Bundle#3 - LL Bundle 2Variants

Tests & Output:

  •  Verify list the list of markets is sent to Hawksearch on bundle level(for any bundle)
  •  Inactivate UK market from bundle #2 → only Australia, Canada, Spain, USA markets are displayed
  •  Activate Sweden market for bundle#3 → Australia, Canada, Spain, UK, USA & Sweden markets are displayed in Hawksearch
  •  Pass
  •  Fail
  •  Pass
  •  Fail

36

Package (kit) published on multiple markets in Optimizely

Input:

  • all kits start with markets: Australia, Canada, Spain, UK, USA

    • package#1 - LL Package 2Variants

    • package#2 - LL Package 2Delete4

    • package#3 - LL Package SingleMarket

Tests & Output:

  •  Verify list the list of markets is sent to Hawksearch on kit level(for any kit)
  •  Inactivate UK market from kit #2 → only Australia, Canada, Spain, USA markets are displayed
  •  Activate Sweden market for kit#3 → Australia, Canada, Spain, UK, USA & Sweden markets are displayed in Hawksearch
  •  Pass
  •  Fail
  •  Pass
  •  Fail

37

https://techromix.atlassian.net/browse/HC-40 | https://techromix.atlassian.net/browse/HC-41

38

Multi-language for products - product & variant level information is sent for each language

Input/Test data:

  • product: LL SHEER CREPE PANT (published in both en & fr)

Tests & Output:

  •  English product level information is sent to Hawksearch English site: Display Name, Description, Long Description
  •  French Product level information is sent to Hawksearch Spanish site: Display Name, Description, Long Description
  •  Variant(s) information is sent to Hawksearch Spanish site: Size | Sku | Mpn | Upc are the same on both English and Spanish sites andColor & Descriptionare language specific
  •  Pass
  •  Fail
  •  Pass
  •  Fail
Warning

https://techromix.atlassian.net/browse/HC-69

https://techromix.atlassian.net/browse/HC-70

39

Multi-language for products

Input/test data:

  • languages: english, french (mapped with spanish in Hawksearch)

  • product#1: DANIEL COOL WOOL JACKET

  • variant #1 for product#1: SKU-39101253

  • product#2: LL SHEER CREPE PANT

Tests & Output

  •  Product#1 created and published on English and NOT published on French → product is found on both English & Spanish sites in Hawksearch, BUT with no information on Spanish
  •  Edit product level information for product#2 on French → edited info is visible in Hawksearch on the Spanish site
  •  Pass
  •  Fail
  •  Blocked
  •  Pass
  •  Fail
  •  Blocked

40

Multi-language bundles - bundle & variant level information is sent for each language

Input/Test data:

  • bundle: “LL Bundle 3Variants” (published in both en & fr)

Tests & Output:

  •  English Bundle level information is sent to Hawksearch English site: Display Name Description, Long Description (question)
  •  French Bundle level information is sent to Hawksearch Spanish site: Display Name Description, Long Description (question)
  •  Bundle Entries - Variant(s) information is sent to Hawksearch Spanish site: Size | Sku | Mpn | Upc are the same on both English and Spanish sites andColor & Descriptionare language specific
  •  Pass
  •  Fail
  •  Pass
  •  Fail
Warning

Incremental & Full index issues

https://techromix.atlassian.net/browse/HC-70

https://techromix.atlassian.net/browse/HC-69

41

Multi-language bundles

Input/Test data:

  • languages: English, French (mapped with Spanish in Hawksearch)

  • bundle#1: “LL Bundle English 2” (published only in en)

  • bundle#2: “LL Bundle Linked” (published in both en & fr)

Tests & Output:

  •  Verify that Bundle#1 is found on both English & Spanish sites in Hawksearch, BUT with no information on Spanish
  •  Edit bundle#2 information on French → edited info is visible in Hawksearch on the Spanish site

  •  Pass
  •  Fail
  •  Blocked

  •  Pass
  •  Fail
  •  Blocked

Info

Blocked by Variant description and Color issues

  • Luminos-Spanish site shows bundle that is not published in french : “LL Bundle PrimaryOnly”

  • Preview page for Luminos-Spanish site will show information for products/bundle/packages if the following fields have Preview Mapping set from Workbench: Display Name, Description, Price, URL

42

Multi-language packages - package & variant level information is sent for each language

Input/Test data:

  • package: “LL Package 2Variants” (published in both en & fr)

Tests & Output:

  •  English Package level information is sent to Hawksearch English site: Display Name, Description, Long Description (question)
  •  French Package level information is sent to Hawksearch Spanish site: Display Name, Description, Long Description (question)
  •  Package Entries - Variant(s) information is sent to Hawksearch Spanish site: Size | Sku | Mpn | Upc are the same on both English and Spanish sites andColor & Descriptionare language specific
  •  Pass
  •  Fail
  •  Pass
  •  Fail
Warning

https://techromix.atlassian.net/browse/HC-70

https://techromix.atlassian.net/browse/HC-69

43

Multi-language packages

Input/Test data:

  • languages: English, French (mapped with Spanish in Hawksearch)

    • package#1: “” (published only for en)

    • package#2: “LL Package 2Variants” (published on both en & fr)

Tests & Output:

  •  Verify that package#1 is found on both English & Spanish sites in Hawksearch, BUT with no information on Spanish
  •  Edit package#2 information on French → edited info is visible in Hawksearch on the Spanish site
  •  Pass
  •  Fail
  •  Blocked
  •  Pass
  •  Fail
  •  Blocked

44

https://techromix.atlassian.net/browse/HC-42 | https://techromix.atlassian.net/browse/HC-43

Default indexing approach supports price indexing only for package types

45

Package (kit) with price on single market

Input:

  • package#1 (Canada market) - LL Package Canada / Price_CAN_CAD / 150 CAD

  • package#2 (Spain market) - LL Package Spain / Price_ESP_EUR / 85 EUR

Tests & Output

  •  Verify price and currency are indexed for package 1&2 (boost-> explain)
  •  Edit price for kit#1→ The updated price is displayed in Hawksearch for the correct market/ currency
  •  Delete price for kit#2 → The price in Hawksearch is deleted and the updated field is empty
  •  Pass
  •  Fail
  •  Pass
  •  Fail

46

Package (kit) with multi-currency prices

Input:

  • package#1 | package#2 - LL Package 2Variants | LL Package SingleMarket

  • 5 markets for each package

    • Australia / Price_AUS_AUD / A$110 | A$180

    • Canada / Price_CAN_CAD / CA$150 | CA$200

    • Spain / Price_ESP_EUR / 75EUR | 85EUR

    • UK / Price_UK_GBP / 90 | -

    • US / Price_US_USD / $130 |

Tests & Output

  •  Verify that each price and currency are indexed and displayed as separate fields for any package (boost-> explain)
  •  Edit price for Australia Market in package#1→ The updated price is displayed in Hawksearch for the correct market/ currency
  •  Delete price for Spain Market in package#2 → price is deleted from Hawksearch from the kit & prices from the other markets are not affected
  •  Pass
  •  Fail
  •  Pass
  •  Fail

47

https://techromix.atlassian.net/browse/HC-47 | https://techromix.atlassian.net/browse/HC-48

Default indexing approach supports price indexing only for package types

48

Package with inventory for single warehouse

Input:

  • package#1 (Canada market) - LL Package Canada (Inventory_Toronto : 455)

  • package#2 (Spain market) - LL Package Spain (Inventory_Madrid: 1250)

Tests & Output

  •  correct inventory is displayed for each package in Hawksearch
  •  remove the market for package#1
    •  market is deleted and the updated field is empty in Hawksearch
    •   price and inventory remain in Opti and are indexed in Hawsearch
  •  Delete the inventory for package#2 → inventory in Hawksearch is deleted and the updated field is empty
  •  Pass
  •  Fail
  •  Pass
  •  Fail

49

Package with inventory in multiple warehouses

Input:

  • package#1 | package#2 - “LL Package SingleMarket” | “LL Package 2Variants”

  • 5 markets for each package

    • Australia / Inventory_Sydney / 35 | 202

    • Canada / Inventory_Toronto / 25 | 201

    • Spain / Inventory_Madrid / 30 | 203

    • UK / Inventory_London / - | 205

    • US / Inventory_Los Angeles / - | 204

Tests & Output

  •  inventory displayed in different line items on the package level in Hawksearch
  •  correct inventory is displayed for each warehouse
  •  remove Australia market for package#1
    •  market is deleted from Hawksearch from the package
    •  price and inventory remain in Opti and are indexed in Hawksearch
    •  the other warehouses are not affected
  •  delete inventory for package#2 in Australia market → inventory in Hawksearch is deleted and the updated field is empty
  •  Pass
  •  Fail
  •  Pass
  •  Fail

Opti setup: “2 websites” variation

Expand
title2 websites (2 pagetypes standard, locationitem) | 2 catalogs: multi-language & multi-market | products-variants | bundle-variants | packages-variants | categories

Scenario(s) + steps

Full Indexing Status

Incremental Indexing Status

Notes

1

Manual / Scheduled Run

Manual / Scheduled Run

2

https://techromix.atlassian.net/browse/HC-36 | https://techromix.atlassian.net/browse/HC-37

CMS - Fields to check: SiteId | MetaTitle | Keywords | BackgroundImage | MainBody | Coordinates | Id | Name | StartPublish | StopPublish | IndexedOn | ContentLink | ParentLink | ItemType | Url |

3

CMS - Standard & Location Item page types are indexed

  • Create a Standard page & a Location Item page for Site A → run the indexing job → verify that the SiteId is for Site A

  • Update the page → run the indexing job → verify updates are available in Hawksearch

  • Delete the page → run the indexing job → verify it is deleted in Hawksearch

  •  Pass
  •  Fail
  •  Pass
  •  Fail
Warning

https://techromix.atlassian.net/browse/HC-71

4

CMS - Other page types are NOT indexed

  • Create a Blog Item page & a Two Column Landing Page → run the indexing job → verify it is NOT available in Hawksearch

  •  Pass
  •  Fail
  •  Pass
  •  Fail

5

NO CMS - Catalog only setup

  • Verify that no CMS changes to Standard or Location Item page types (create, update, delete) are indexed

  •  Pass
  •  Fail
  •  Pass
  •  Fail

6

Categories & category structure

7

Verify that the Category structure for each Catalog is sent to Hawksearch

  •  Pass
  •  Fail
  •  Pass
  •  Fail

8

Edit the Category structure on Catalog A and verify it is updated in Hawksearch → The catalog structure in Site B is not affected

  •  Pass
  •  Fail
  •  Pass
  •  Fail

9

Products / Bundles / Packages

10

Edit in Catalog A:

  • product, variant, bundle, package in one language → verify the changes are displayed in Hawksearch and Catalog B is not affected

  • Prices in different currencies → verify the changes are displayed in Hawksearch and Catalog B is not affected

Test Data/Input:

Product + variant: LUCIEN COTTON TWILL COAT

Package: LL Package 2Delete3

Bundle: LL Bundle Primary2delete

  •  Pass
  •  Fail
  •  Pass
  •  Fail

11

Delete categories from catalog B

Output:

  • Catalog A is not affected

  • the category is not available

  • the products under that category are not available

  • the variants under that category are not available

  •  Pass
  •  Fail
  •  Pass
  •  Fail

12

Delete products/ variants/ bundles / packages in Catalog B

Test Data/Input:

Product + variant: LL JADE HIGH BOOT

Package: LL Package 2Delete5

Bundle: LL Bundle 2delete2

Output:

  • Catalog A is not affected

  • the category is not available

  • the products under that category are not available

  • the variants under that category are not available

  •  Pass
  •  Fail
  •  Pass
  •  Fail

13

Move from Site A to Site B:

  • a category → verify the Catalog ID and ParentLink are updated

  •  LL Jackets
  •  LL Shoes
  • a product → verify the Catalog ID, Category and ParentLink are updated

  •  LL SHEER CREPE PANT
  • a variant → verify the Catalog ID, Category and ParentLink are updated

  •  Morgan sneaker
  •  Nubuc loafer
  • a bundle → verify the Catalog ID, Category and ParentLink are updated

  •  LL Bundle Primary2delete
  • a package (kit) → verify the Catalog ID, Category and ParentLink are updated

  •  LL Package 2Delete1
  •  Pass
  •  Fail
  •  Pass
  •  Fail
  •  Blocked