Test query pipeline changes

This is for:

query pipelines and their rules are powerful tools that let you manage different query situations with great flexibility. This flexibility, however, may become overwhelming in complexity, which is why it’s important to test your query pipeline changes before applying them.

Leading practices

Test each query pipeline modification with a JavaScript Search page on a test pipeline before applying it to the production pipeline.
Take advantage of the query pipeline A/B Testing feature to partially put the modification in production, allowing you to evaluate the effect on real queries made by real users.

To test query pipeline changes

Create a test pipeline to be used only for test purposes, if not already done.

You can duplicate your production pipeline, the one used by the search interface to which you want to make a change (see Manage query pipelines). This way, the only difference between the production and the test pipeline will be the change you’ll make. Rename the duplicated pipeline to something meaningful.

For example, you duplicate your Community pipeline and rename the duplicate as Community_TEST_duplicate_yyyy-mm-dd so you’ll know when it was duplicated and maybe delete it when outdated, rather than creating a new duplicate.

Make the desired specific change to your test pipeline rules, if not already done (see Manage query pipelines).
Test your pipeline change in the Content Browser:
1. On the Query Pipelines (platform-ca | platform-eu | platform-au) page, click the desired pipeline, and then click More > Open in Content Browser in the Action bar.
2. On the Content Browser (platform-ca | platform-eu | platform-au) page, perform queries to validate the change you made to this specific pipeline.

Test a pipeline change in a JavaScript Search page just for your session:

Access the JavaScript Search page for which you want to test the pipeline change.
Perform a query that would meet the condition to make your change visible. Because the search page is still using the production pipeline, the change shouldn’t be visible.

In the browser address box, add the pipeline= query string parameter followed by the name of your test pipeline, and then run the query again. This time, the query will go through your test pipeline. This method only affects your queries, not anyone else. Depending on the query parameter position, prefix pipeline=:

When pipeline= is the first query parameter, prefix it with ?.

Example

https://search.mycompany.com?pipeline=Community_TEST_duplicate_2015-11-05

When pipeline= isn’t the first query parameter, prefix it with &.

Example

https://search.mycompany.com?param1=value1&pipeline=Community_TEST_duplicate_2015-11-05

Notes

The pipeline= query string parameter isn’t recognized in JavaScript Search versions prior to v1.0.139. Ensure that your search page meets this criterion (see Identifying the Coveo JavaScript Search Version).
The pipeline= query string parameter must be before the # in the URL:

https://search.mycompany.com?param1=value1&pipeline=Community_TEST_duplicate_2015-11-05#q=keyword&sort=relevancy

Perform the same query that meets the condition to make your change visible and ensure that it behaves as expected.

When you’re satisfied with your change, consider first testing your change on a fraction of the production traffic using A/B Testing.
1. Consider creating and using a usage analytics report to compare key metrics for the A and B query pipeline, and confirm the improvement over a given period.
2. When you’re entirely sure that you want to bring your change to the production pipeline, copy the changed rule from the test pipeline (B) to the production pipeline (A) (see Copy a rule to another pipeline).
Remove the pipeline= query string parameter from the search page URL, and then perform the same query that meets the condition. This makes your change visible, allowing you to ensure that the search page behaves as expected.