Category response languages are applied for tests that include a category as an input and not search text. Search Testing should support the exact same languages as your production site, if you want the complete set of results returned by the search engine to be visible in Search Testing. Note that it’s unlikely a site visitor would see all of those results, because most sites are coded to filter out results that aren’t in a site visitor’s language. If you’d like for Search Testing to display what a given site visitor sees, or results in a subset of the supported languages, specify those languages directly. Otherwise, copy your response language settings from your production site to see results in all languages.
Viewing Results in All Languages
To display results in all languages supported by your production site:
Copy all components of the following classes that exist in the production environment:
atg.search.routing.command.search.StringConstraint
atg.search.routing.command.search.ConstraintsGroup
atg.search.routing.command.search.ConstraintsGroupCopy the value in the
documentSetConstraintsproperty of the production Query Request component to the corresponding component in/atg/commerce/search/catalog.
Viewing Results in a Subset of Languages
The way in which you provide category response languages that are a subset of those supported by the production environment depends on the number of languages you want to use.
To view results in a single language, follow the steps in this procedure, which specify support for English:
Create a properties file for a component of class
atg.search.routing.command.search.StringConstraintas follows:$class=atg.search.routing.command.search.StringConstraint
$scope=request
property=language
operation=equal
value=EnglishSave the properties file in a Search Testing directory in your local configuration layer, such as
<ATG9dir>/home/localconfig/atg/commerce/search.Register the new component with the Query Request component in
/atg/commerce/search/catalogby setting thedocumentSetConstraintsproperty to the type of constraint being used. For example:documentSetConstraints=/atg/commerce/search/StringConstraint
To view results in multiple languages that are a subset of the total list of languages supported for production, you need to create several components, one for each language you want to support. For example, to view results in French and English, follow these steps:
Create a properties file for an English String Constraint component of class
atg.search.routing.command.search.StringConstraintin a Search Testing directory in your local configuration layer, such as<ATG9dir>/home/localconfig/atg/commerce/search:$class=atg.search.routing.command.search.StringConstraint
$scope=requestproperty=language
operation=equal
value=EnglishIn the same location, create a similar component called French String Constraint with French as the language:
$class=atg.search.routing.command.search.StringConstraint
$scope=requestoperation=equal
property=language
value=FrenchIn the same location, create a Constraint Group component that will combine the constraints in the String Constraint components that you created.
$class=atg.search.routing.command.search.ConstraintsGroup
$scope=request
constraints=EnglishStringConstraint,FrenchStringConstraint
operation=orRegister the new component with the Query Request component in
/atg/commerce/search/catalogby setting thedocumentSetConstraintsproperty to the Constraints Group component being used. For example:documentSetConstraints=StringConstraint
