Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to Docker based integration tests #500

Merged
merged 3 commits into from
Feb 11, 2018
Merged

Move to Docker based integration tests #500

merged 3 commits into from
Feb 11, 2018

Conversation

dadoonet
Copy link
Owner

Sadly we have to run now our tests sequentially
If we move the Docker start as a Maven pre-integration process we will be able to run that again in parallel.

Closes #496.

Sadly we have to run now our tests sequentially
If we move the Docker start as a Maven pre-integration process we will be able to run that again in parallel.

Closes #496.
@dadoonet dadoonet added new For new features or options test Related to tests only labels Feb 11, 2018
@dadoonet dadoonet added this to the 2.5 milestone Feb 11, 2018
@dadoonet dadoonet self-assigned this Feb 11, 2018
It's not available as a Docker image.
It's not available as a Docker image.
@dadoonet dadoonet merged commit 895a211 into master Feb 11, 2018
@dadoonet dadoonet deleted the pr/it-docker branch February 11, 2018 20:00
dadoonet added a commit that referenced this pull request Feb 19, 2018
With recent changes like #500 and #514 it takes much more time to run all tests from the IDE when elasticsearch is not running yet locally.
The reason is that we start a new elasticsearch test container for every class. Starting a container can take some time.

We should try to reduce that and share the same docker instance for all tests.

Closes #516
dadoonet added a commit that referenced this pull request Feb 19, 2018
With recent changes like #500 and #514 it takes much more time to run all tests from the IDE when elasticsearch is not running yet locally.
The reason is that we start a new elasticsearch test container for every class. Starting a container can take some time.

We should try to reduce that and share the same docker instance for all tests.

Closes #516
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new For new features or options test Related to tests only
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant