Test Suite

Overview

The Test Suite project provides example implementations and integrations for Bloomreach Content. You can use it to review a variety of use cases and reference configurations.

Purpose

Run the Test Suite project to review example implementations and integrations across different features of Bloomreach Content.

Project Information

The Test Suite project is maintained by the Bloomreach engineering team for internal testing. It also serves as a resource for developers who want to explore example implementations and integrations.

The test suite is provided as-is and is not officially supported by Bloomreach. For questions, use the community forum.

Clone, Build, and Run the Test Suite

Follow these steps to set up and run the Test Suite on your development machine:

Clone the brxm Git repository:

git clone https://github.com/bloomreach/brxm.git

Check out the desired release tag, for example:
```
git checkout brxm-14.3.3
```
Change to the testsuite directory:
```
cd testsuite
```
Build and run the hippo-testsuite project as you would with any Bloomreach Content project. For detailed instructions, see Building a Project and Running a Project.

After starting the project, access the web applications at the following URLs:

http://localhost:8080/cms/
http://localhost:8080/cms/console/
http://localhost:8080/cms/repository/
http://localhost:8080/site/

Example Implementations in the Test Suite

The Test Suite includes a variety of example implementations. The following list highlights some of the available examples:

French channel:
```
http://localhost:8080/site/demosite_fr
```
Faceted Navigation:
```
http://localhost:8080/site/faceted
```
Form component:
```
http://localhost:8080/site/form
```
Search (demonstrates both standard Jackrabbit date range search and optimized Hippo date range search):
```
http://localhost:8080/site/search
```

Spring MVC Bridge:

http://localhost:8080/site/contact-springmvc

Additional examples are available in the Test Suite. Review the project code and inspect the configuration in the console to understand how each example is implemented.