Test Suite
Introduction
Goal
Run the Test Suite project to see examples of many different implementations and integrations.
Background
The Test Suite project is used by BloomReach's engineering team to test many different implementations and integrations. For other developers, it serves as a collection of example implementations and integrations.
Please note that the test suite is provided to the community as-is and is not supported by BloomReach. However, if you have a question about the test suite, feel free to post it at the community forum.
Clone, Build, and Run the Test Suite
Clone the hippo-testsuite Git repository on your development machine:
git clone https://code.onehippo.org/cms-community/hippo-testsuite.git
Alternatively, download the repository as a zip file from code.onehippo.org.
To be able to build the master branch, configure the Bloomreach Experience Manager Maven snapshot repository as described at Build Bloomreach Experience Manager from source.
Tags are stable and do not require the snapshot repository.
Build and run the hippo-testsuite project like any other Bloomreach Experience Manager implementation project.
The different webapps are available at the usual URLs:
http://localhost:8080/cms/ http://localhost:8080/cms/console/ http://localhost:8080/cms/repository/ http://localhost:8080/site/
Examples in the Test Suite
Below is a non-exhaustive list of examples in the test suite that you may find interesting:
- French channel:
http://localhost:8080/site/demosite_fr
- Faceted Navigation:
http://localhost:8080/site/faceted
- Form component:
http://localhost:8080/site/form
- Search (comparing slow Jackrabbit date range search with fast Hippo date range search):
http://localhost:8080/site/search
- Spring MVC Bridge:
http://localhost:8080/site/contact-springmvc
There are many more examples to be found in the test suite. Explore the project's code and configuration (in the console) to learn how the examples are implemented.