druid/integration-tests-ex/cases/resources
Paul Rogers cfed036091
Add the new integration test framework (#12368)
This commit is a first draft of the revised integration test framework which provides:
- A new directory, integration-tests-ex that holds the new integration test structure. (For now, the existing integration-tests is left unchanged.)
- Maven module druid-it-tools to hold code placed into the Docker image.
- Maven module druid-it-image to build the Druid-only test image from the tarball produced in distribution. (Dependencies live in their "official" image.)
- Maven module druid-it-cases that holds the revised tests and the framework itself. The framework includes file-based test configuration, test-specific clients, test initialization and updated versions of some of the common test support classes.

The integration test setup is primarily a huge mass of details. This approach refactors many of those details: from how the image is built and configured to how the Docker Compose scripts are structured to test configuration. An extensive set of "readme" files explains those details. Rather than repeat that material here, please consult those files for explanations.
2022-08-24 17:03:23 +05:30
..
data/batch_index Add the new integration test framework (#12368) 2022-08-24 17:03:23 +05:30
indexer Add the new integration test framework (#12368) 2022-08-24 17:03:23 +05:30
README.md Add the new integration test framework (#12368) 2022-08-24 17:03:23 +05:30

README.md

Test Data

This directory contains resources, such as test data, mounted into Druid indexer container at /resources. That name is chosen for backward compatibility with the previous IT version that mounted /src/test/resources to that mount point. See the indexer node in docker-compose.yaml for BatchIndex for the actual volume mount.

The many indexer specs expect data to be at /resources/data/batch_index/json/spec.json, where spec is the name of some ingest spec. The structure here was chosen to allow the existing specs to be reused without change.

Put data for the Indexer in this folder. Put files to be used by tests in /src/test/resources. That way, we only mount into the container the data which the server needs. Resources which tests need, such as queries, specs and other resources, are on the class path of the test, but are not visible to the server.

Paths within this folder are the same as the former /src/test/resources folder so that the many indexer specs don't have to change.