honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/sql/test-utils/build.gradle

26 lines
841 B
Groovy
Raw Normal View History

Closer to compiling Original commit: elastic/x-pack-elasticsearch@630bd7967d7ef30fc313353cb2e4cf3dfa29c53c
2017-06-20 14:03:53 -04:00
apply plugin: 'elasticsearch.build'
Move all sql integration tests into qa (elastic/x-pack-elasticsearch#2432) Builds on elastic/x-pack-elasticsearch#2403 to move all of sql's integration testing into qa modules with different running server configurations. The big advantage of this is that it allows us to test the cli and jdbc with security present. Creating a project that depends on both cli and jdbc and the server has some prickly jar hell issues because cli and jdbc package their dependencies in the jar. This works around it in a few days: 1. Include only a single copy of the JDBC dependencies with careful gradle work. 2. Do not include the CLI on the classpath at all and instead run it externally. I say "run it externally" rather than "fork it" because Elasticsearch tests aren't allowed to fork other processes. This is forbidden by seccomp on linux and seatbelt on osx and cannot be explicitly requested like additional security manager settings. So instead of forking the CLI process directly the tests interact with a test fixture that isn't bound by Elasticsearch's rules and *can* fork it. This forking of the CLI has a nice side effect: it forces us to make sure that things like security and connection strings other than `localhost:9200` work. The old test could and did work around missing features like that. The new tests cannot so I added the ability to set the connection string. Configuring usernames and passwords was also not supported but I did not add support for that, only created the failing test and marked it as `@AwaitsFix`. Original commit: elastic/x-pack-elasticsearch@560c6815e3e03306270a2affd758763f34613891
2017-09-21 09:58:52 -04:00
description = 'Shared test utilities for jdbc and cli protocol projects'
Closer to compiling Original commit: elastic/x-pack-elasticsearch@630bd7967d7ef30fc313353cb2e4cf3dfa29c53c
2017-06-20 14:03:53 -04:00
dependencies {
Start on round trip tests I don't want to dig too closely into the ES integration yet because it being fixed by Costin so instead I'll make an example for round trip testing. Original commit: elastic/x-pack-elasticsearch@4d8fbc571e1559e2859d9096bb4a6a68a3d06b56
2017-06-22 18:21:55 -04:00
compile "junit:junit:${versions.junit}"
compile "org.hamcrest:hamcrest-all:${versions.hamcrest}"
Move all sql integration tests into qa (elastic/x-pack-elasticsearch#2432) Builds on elastic/x-pack-elasticsearch#2403 to move all of sql's integration testing into qa modules with different running server configurations. The big advantage of this is that it allows us to test the cli and jdbc with security present. Creating a project that depends on both cli and jdbc and the server has some prickly jar hell issues because cli and jdbc package their dependencies in the jar. This works around it in a few days: 1. Include only a single copy of the JDBC dependencies with careful gradle work. 2. Do not include the CLI on the classpath at all and instead run it externally. I say "run it externally" rather than "fork it" because Elasticsearch tests aren't allowed to fork other processes. This is forbidden by seccomp on linux and seatbelt on osx and cannot be explicitly requested like additional security manager settings. So instead of forking the CLI process directly the tests interact with a test fixture that isn't bound by Elasticsearch's rules and *can* fork it. This forking of the CLI has a nice side effect: it forces us to make sure that things like security and connection strings other than `localhost:9200` work. The old test could and did work around missing features like that. The new tests cannot so I added the ability to set the connection string. Configuring usernames and passwords was also not supported but I did not add support for that, only created the failing test and marked it as `@AwaitsFix`. Original commit: elastic/x-pack-elasticsearch@560c6815e3e03306270a2affd758763f34613891
2017-09-21 09:58:52 -04:00
compile "org.elasticsearch.test:framework:${versions.elasticsearch}"
Closer to compiling Original commit: elastic/x-pack-elasticsearch@630bd7967d7ef30fc313353cb2e4cf3dfa29c53c
2017-06-20 14:03:53 -04:00
}
More of precommit Original commit: elastic/x-pack-elasticsearch@b106bde2f0707de128b4555eb5b358318ff254c0
2017-06-21 12:12:19 -04:00
Some more tests Closer to `gradle check -xforbiddenPatterns` passing. Original commit: elastic/x-pack-elasticsearch@fbce74a1f30d755bdbecdd721b26f49fa04b1335
2017-07-06 15:58:12 -04:00
thirdPartyAudit.excludes = [
// Referneced by the test:framework but not used
'org.apache.tools.ant.BuildException',
'org.apache.tools.ant.DirectoryScanner',
'org.apache.tools.ant.Task',
'org.apache.tools.ant.types.FileSet',
'org.easymock.EasyMock',
'org.easymock.IArgumentMatcher',
'org.jmock.core.Constraint',
]
More of precommit Original commit: elastic/x-pack-elasticsearch@b106bde2f0707de128b4555eb5b358318ff254c0
2017-06-21 12:12:19 -04:00
/* Elasticsearch traditionally disables this for test utilities because it is
* hard to configure and (hopefully) much less important for tests than
* production code. */
dependencyLicenses.enabled = false