Search Testing replicates search conditions on your production site, so you must configure Search Testing components with the same property values as their production counterparts. Usually, you can copy property values from the production component to the corresponding Search Testing component. If your production site is coded to overwrite some properties in components with dynamic values provided by site JSP pages, when you are copying property values, be sure to check your JSPs for tags that update values. If you find any, you’ll need to update the Search Testing component with the static value that is most often passed to the JSP.
Although you need to make updates to some component properties, a number of properties are provided for you and in fact, if you change them, Search Testing will overwrite your changes. Some components, such as form handlers, automatically derive property values from the production instance of that component, so although it’s vital that the values of these two components are identical, they will be by default.
Note: You may add additional instances of Facet Search Tools and Search Configuration Request Processor, but you should not overwrite the instances defined in Search Testing.
If you have created or updated any of the following components on your production site, create or update the corresponding Search Testing components. Most resources will have the same name and location in both instances, though any differences are noted in the table below:
Resource | Property |
|---|---|
Component: MultisiteConstraint Class: | all properties |
Component: Class: | all properties |
Component: Class: | all properties |
Component: Class |
|
Search Testing Instance: Production Instance: a component of class |
|
