kit-data-manager / kit-data-manager/pit-service

Run Elasticsearch-dependent tests also in CI

Open
#244 0 comments 0 reactions 0 assignees View on GitHub
maintenance
Dominant language
Java
Stars
3
Forks
4
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**

We have a few deactivated tests for Elasticsearch which currently need to be run manually.

**Describe the solution you'd like**

There is a simple solution to have an ES container spawned just for testing, using this in the build gradle file:

```
testImplementation "org.testcontainers:testcontainers:1.20.0"
testImplementation "org.testcontainers:junit-jupiter:1.20.0"
testImplementation "org.testcontainers:elasticsearch:1.20.0"
```

But: It has to be tested if this actually works in the GitHub CI.

**Describe alternatives you've considered**

Boring scripts, lame mocking, ...

**Additional context**

-

Contributor guide

Open the contributing guide

Research direction

Start by locating the deactivated Elasticsearch tests and the build Gradle file, then verify the proposed Testcontainers dependencies in GitHub CI. Done means those tests run automatically in CI against an Elasticsearch container without manual setup.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch, github-actions, java
Domain
ci-cd, search, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.