4

I currently have the requirement to set up page level tests to test two different pages against each other. I am doing this in the Experience Optimization application using the 'use existing' button when adding pages to test against. We are looking at testing pages based on different templates, however on the Sitecore community pages it states that:

"Page Level Tests don’t support testing items with different templates. All the items that are included in the test must have the same template." - https://community.sitecore.net/technical_blogs/b/sitecore_development_team/posts/the-difference-between-the-content-test-and-page-level-test

I have managed to set up a page level test so the user sees one of two pages based on two different templates. Is this functionality supported as it seems to be or am I going to hit a snag down the line based on what the community document states?

Improve this question
2
  • What steps did you do to set-up the page level test that uses content from multiple templates? When I try to reproduce that I get the template validation restriction. Also, what version of SC?
    – James Williamson
    Commented Aug 17, 2017 at 19:14
  • We are using Sitecore 8.0 and the steps we followed were: go to experience optimisation, create page test, select a page, add page to test against, use existing page, select a page with a different template and then review and start.
    – Calum
    Commented Aug 25, 2017 at 8:24

1 Answer 1

Reset to default
0

I'm going to take a stab at answering this generally, since I don't have the particulars of your specific issue.

All tests in Sitecore (Page tests, content tests, component tests, the tests that run as part of personalization…) are based on a single test definition template. The variations that I'm aware of are those related to editor presentation and workflow options.

If you've figured out how to hack the page tests to use different templates, and you're getting test results out of them, I can't envision a scenario where you'd run into trouble. Especially, because tests are designed to run for a short period of time; we test, we learn something and repeat. We're not (at least, not yet) tracking the history of tests & test results.

The last comment relates to having to select from different templates. Templates are typically tied to data sources. And, we don't typically test different content against one another - an article against an event… If you're Sitecore architecture requires that you make template variations to affect presentation, there's probably a better way -- Component based design.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.