Index Variants as children of parents
- Vidhya Ananthanarayanan
Testing Support
1- Useful links & tips
Hawksearch Dashboard (testing)- https://test.hawksearch.net/ (nracz / Temp1234 )
Optimizely (testing): https://qa-hawksearch.luminoslabs.com/episerver/
check fields: Boost → Explain → Info & Field Matches
add Price & Inventory fields per market: Workbench → Data Configuration → Fields
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
Notes on Foundation:
Following variant fields are NOT indexed or rolled up into the parent(product/bundle/package) as part of this approach:
Child_Color, Child_Size, Child_DisplayName, Child_Code, Child_Url
Inventory_{WarehouseCode} , Price_{MarketId}_{Currency}
For Bundles and Packages only Variant entries(components) are indexed, anything else is NOT.
Inventory_{WarehouseCode} , Price_{MarketId}_{Currency} are indexed only for Packages.
ImageAlt, ImageURL are indexed only for products in foundation.
Opti setup: most common
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
| Pass Fail | Pass Fail |
|
4 | CMS - Other page types are NOT indexed
| Pass Fail | Pass Fail |
|
5 | NO CMS - Catalog only setup
| Pass Fail | Pass Fail |
|
6 | ||||
7 | Verify that the Category structure is sent to Hawksearch
|
| ||
8 | Edit the Category structure and verify it is updated in Hawksearch |
| ||
9 | Delete categories and verify in Hawksearch that:
|
| ||
10 | Product-variant catalog structure
|
| ||
11 | Variant-only catalog structure
|
| ||
12 | Products - Fields to check
| |||
13 | Verify that product fields are sent to Hawksearch for each product |
| ||
14 | Edit product information and verify that updates are sent to Hawksearch
|
| ||
15 | Delete product information and verify that it is also removed in Hawksearch |
| ||
16 | Update Parent of product and verify the Category ID and Parent link is updated Test data/Input
|
| ||
17 | Product belongs to several categories
|
| ||
18 | Product belongs to several categories
|
| ||
19 | Delete a product’s Primary category Input (tip: backup & restore DB)
Output: for product#1(under Primary category only): for product#2(under Primary and secondary categories): |
| ||
20 | Delete product and verify the product is removed in Hawksearch Test data:
|
| ||
21 | https://techromix.atlassian.net/browse/HC-32 | https://techromix.atlassian.net/browse/HC-34 Bundles - Fields to check:
| |||
22 | Bundle level information is sent to Hawksearch Input/Test data:
Output: |
| ||
23 | Update Parent of a bundle and verify the Category ID and Parent link is updated Test data/Input
|
| ||
24 | Bundle belongs to several categories Test data:
Output: |
| ||
25 | Delete a Bundle’s Primary category Input:
Output: bundle#1(under Primary category only): bundle#2(under Primary and secondary categories): |
| ||
26 | https://techromix.atlassian.net/browse/HC-33 | https://techromix.atlassian.net/browse/HC-35 Packages - Fields to check:
*only variants are considered children | |||
27 | Package level information is sent to Hawksearch Input/Test data:
Output: |
| ||
28 | Update Parent of a package (kit) and verify the Category ID and Parent link is updated Test data/Input
|
| ||
29 | Package (kit) belongs to several categories Test data:
Output: |
| ||
30 | Delete a package (kit)’s Primary category Input(tip for testing: backup & restore DB):
Output: package#1(under Primary category only): package#2(under Primary and secondary categories): |
| ||
31 | https://techromix.atlassian.net/browse/HC-38 | https://techromix.atlassian.net/browse/HC-39 | |||
32 | Product published on multiple markets in Optimizely Input:
Tests & Output: |
| ||
33 | Bundle published on multiple markets in Optimizely Input:
Tests & Output: |
| ||
34 | Package (kit) published on multiple markets in Optimizely Input:
Tests & Output: |
| ||
35 | https://techromix.atlassian.net/browse/HC-40 | https://techromix.atlassian.net/browse/HC-41 | |||
36 | Multi-language for products - product & variant level information is sent for each language Input/Test data:
Tests & Output: |
| ||
37 | Multi-language for products Input/test data:
Tests & Output |
| ||
38 | Multi-language bundles - bundle & variant level information is sent for each language Input/Test data:
Tests & Output: |
| ||
39 | Multi-language bundles Input/Test data:
Tests & Output:
|
|
|
|
40 | Multi-language packages - package & variant level information is sent for each language Input/Test data:
Tests & Output: |
| ||
41 | Multi-language packages Input/Test data:
Tests & Output: |
| ||
42 | https://techromix.atlassian.net/browse/HC-42 | https://techromix.atlassian.net/browse/HC-43 Default indexing approach supports price indexing only for package types | |||
43 | Package (kit) with price on single market Input:
Tests & Output |
| ||
44 | Package (kit) with multi-currency prices Input:
Tests & Output |
| ||
45 | https://techromix.atlassian.net/browse/HC-47 | https://techromix.atlassian.net/browse/HC-48 Default indexing approach supports price indexing only for package types | |||
46 | Package with inventory for single warehouse Input:
Tests & Output |
| ||
47 | Package with inventory in multiple warehouses Input:
Tests & Output |
|
Opti setup: “2 websites” variation
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 |
| ||
4 | CMS - Other page types are NOT indexed
|
| ||
5 | NO CMS - Catalog only setup
|
| ||
6 | Categories & category structure | |||
7 | Verify that the Category structure for each Catalog is sent to Hawksearch
|
| ||
8 | Edit the Category structure on Catalog A and verify it is updated in Hawksearch → The catalog structure in Site B is not affected |
| ||
9 | Products / Bundles / Packages | |||
10 | Edit in Catalog A:
Test Data/Input: Product + variant: LUCIEN COTTON TWILL COAT Package: LL Package 2Delete3 Bundle: LL Bundle Primary2delete |
| ||
11 | Delete categories from catalog B Output:
|
| ||
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:
|
| ||
13 | Move from Site A to Site B:
|
|
|