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

Number of utilities for writing gradle integration tests #32282

Merged
merged 1 commit into from
Jul 25, 2018

Conversation

alpar-t
Copy link
Contributor

@alpar-t alpar-t commented Jul 23, 2018

These are collected from a number of open PRs and are required to
improove existing and write more readable future tests.
I am extracting them to their own PR hoping to be able to merge and use
them sooner.

These are collected from a number of open PRs and are required to
improove existing and write more readable future tests.
I am extracting them to their own PR hoping to be able to merge and use
them sooner.
@alpar-t alpar-t added >test Issues or PRs that are addressing/adding tests :Delivery/Build Build or test infrastructure labels Jul 23, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

Copy link
Member

@nik9000 nik9000 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These do seem useful to me but I'd prefer they go in when we use them for the first time just because it feels more in line with how we write software. But they do seem nice and if you need them in a few PRs I totally understand wanting them now so your in flight PRs are easier to review. I'm +1 on merging so long as you go back through them when you current crop of PRs is done and remove what you don't end up needing.

@alpar-t
Copy link
Contributor Author

alpar-t commented Jul 23, 2018

Thanks Nik! I agree with you about adding these when needed, they all came out of PRs where these were used and wished fro them to be there in others I was working on. I'll make sure there's no unused ones in the end. Their small pieces of functionality, and repeating them wouldn't be that bad, but I think it makes the test better, unfortunately that's exactly the context missing here.

@alpar-t alpar-t merged commit 6aea829 into elastic:master Jul 25, 2018
@alpar-t alpar-t deleted the gradle-test-utils branch July 25, 2018 06:23
alpar-t added a commit that referenced this pull request Jul 25, 2018
These are collected from a number of open PRs and are required to
improove existing and write more readable future tests.
I am extracting them to their own PR hoping to be able to merge and use
them sooner.
jasontedor added a commit that referenced this pull request Jul 25, 2018
* elastic/master:
  Number of utilities for writing gradle integration tests (#32282)
  Determine the minimum gradle version based on the wrapper (#32226)
  Enable FIPS JVM in CI (#32330)
  Fix JarHell on X-Pack protocol
jasontedor added a commit that referenced this pull request Jul 25, 2018
* elastic/6.x:
  Tests: Fix XPack upgrade tests (#32352)
  Remove invalid entry from 6.3.2 release notes
  Number of utilities for writing gradle integration tests (#32282)
  Determine the minimum gradle version based on the wrapper (#32226)
  Enable FIPS JVM in CI (#32330)
  Build: Fix jarHell error I caused by last backport
  Build: Shadow x-pack:protocol into x-pack:plugin:core (#32240)
jasontedor added a commit to jasontedor/elasticsearch that referenced this pull request Jul 25, 2018
* ccr:
  Number of utilities for writing gradle integration tests (elastic#32282)
  Determine the minimum gradle version based on the wrapper (elastic#32226)
  Enable FIPS JVM in CI (elastic#32330)
  Build: Fix jarHell error I caused by last backport
  Use shadow plugin in ccr/qa
  Fix JarHell on X-Pack protocol
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team >test Issues or PRs that are addressing/adding tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants