Build failed in Jenkins: Geode-nightly #1239

2018-06-27 Thread Apache Jenkins Server 
See 

--
[...truncated 49.58 KB...]
> Task :geode-connectors:spotlessJava
> Task :geode-connectors:spotlessJavaCheck
> Task :geode-connectors:spotlessCheck
> Task :geode-connectors:test
> Task :geode-core:assemble
> Task :geode-core:checkMissedTests
> Task :geode-core:spotlessJava
> Task :geode-core:spotlessJavaCheck
> Task :geode-core:spotlessCheck
> Task :geode-core:test
> Task :geode-cq:assemble

> Task :geode-cq:compileTestJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-cq:processTestResources
> Task :geode-cq:testClasses
> Task :geode-cq:checkMissedTests
> Task :geode-cq:spotlessJava
> Task :geode-cq:spotlessJavaCheck
> Task :geode-cq:spotlessCheck
> Task :geode-cq:test
> Task :geode-experimental-driver:jar
> Task :geode-experimental-driver:javadoc
> Task :geode-experimental-driver:javadocJar
> Task :geode-experimental-driver:sourcesJar
> Task :geode-experimental-driver:signArchives SKIPPED
> Task :geode-experimental-driver:assemble

> Task :geode-experimental-driver:compileTestJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-experimental-driver:processTestResources
> Task :geode-experimental-driver:testClasses
> Task :geode-experimental-driver:checkMissedTests
> Task :geode-experimental-driver:spotlessJava
> Task :geode-experimental-driver:spotlessJavaCheck
> Task :geode-experimental-driver:spotlessCheck
> Task :geode-experimental-driver:test
> Task :geode-json:assemble
> Task :geode-json:compileTestJava NO-SOURCE
> Task :geode-json:processTestResources
> Task :geode-json:testClasses
> Task :geode-json:checkMissedTests NO-SOURCE
> Task :geode-json:spotlessJava
> Task :geode-json:spotlessJavaCheck
> Task :geode-json:spotlessCheck
> Task :geode-json:test NO-SOURCE
> Task :geode-old-versions:javadoc NO-SOURCE
> Task :geode-junit:javadoc
> Task :geode-junit:javadocJar
> Task :geode-junit:sourcesJar
> Task :geode-junit:signArchives SKIPPED
> Task :geode-junit:assemble

> Task :geode-junit:compileTestJava
Note: 

 uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: 

 uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-junit:processTestResources
> Task :geode-junit:testClasses
> Task :geode-junit:checkMissedTests
> Task :geode-junit:spotlessJava
> Task :geode-junit:spotlessJavaCheck
> Task :geode-junit:spotlessCheck
> Task :geode-junit:test
> Task :geode-lucene:assemble

> Task :geode-lucene:compileTestJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-lucene:processTestResources
> Task :geode-lucene:testClasses
> Task :geode-lucene:checkMissedTests
> Task :geode-lucene:spotlessJava
> Task :geode-lucene:spotlessJavaCheck
> Task :geode-lucene:spotlessCheck
> Task :geode-lucene:test
> Task :geode-old-client-support:assemble
> Task :geode-old-client-support:compileTestJava
> Task :geode-old-client-support:processTestResources NO-SOURCE
> Task :geode-old-client-support:testClasses
> Task :geode-old-client-support:checkMissedTests
> Task :geode-old-client-support:spotlessJava
> Task :geode-old-client-support:spotlessJavaCheck
> Task :geode-old-client-support:spotlessCheck
> Task :geode-old-client-support:test
> Task :geode-old-versions:javadocJar
> Task :geode-old-versions:sourcesJar
> Task :geode-old-versions:signArchives SKIPPED
> Task :geode-old-versions:assemble
> Task :geode-old-versions:compileTestJava NO-SOURCE
> Task :geode-old-versions:processTestResources NO-SOURCE
> Task :geode-old-versions:testClasses UP-TO-DATE
> Task :geode-old-versions:checkMissedTests NO-SOURCE
> Task :geode-old-versions:spotlessJava
> Task :geode-old-versions:spotlessJavaCheck
> Task :geode-old-versions:spotlessCheck
> Task :geode-old-versions:test NO-SOURCE
> Task :geode-protobuf:assemble

> Task :geode-protobuf:compileTestJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-protobuf:processTestResources
> Task :geode-protobuf:testClasses
> Task :geode-protobuf:checkMissedTests
> Task :geode-protobuf:spotlessJava
> Task :geode-protobuf:spot

Fwd: Build failed in Jenkins: Geode-nightly #1238

2018-06-27 Thread Anthony Baker 
I cleaned up the workspace which should resolve the rat failure.  Gradle 4.8 
leaves a file behind on first use.

Anthony


> Begin forwarded message:
> 
> From: Apache Jenkins Server 
> Subject: Build failed in Jenkins: Geode-nightly #1238
> Date: June 27, 2018 at 9:36:17 PM PDT
> To: dev@geode.apache.org, bschucha...@pivotal.io, dbar...@pivotal.io, 
> jil...@pivotal.io
> Reply-To: dev@geode.apache.org
> 
> See 
> 
> 
> Changes:
> 
> [github] GEODE-5346: Fix race in LauncherLifecycleCommandsDUnitTest (#2080)
> 
> [bschuchardt] GEODE-1198 CI Failure: 
> DistributedSystemDUnitTest.testConflictingUDPPort
> 
> --
> [...truncated 29.24 KB...]
> 
>> Task :geode-connectors:compileTestJava
> Note: 
> 
>  uses or overrides a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> 
>> Task :geode-connectors:processTestResources
>> Task :geode-connectors:testClasses
>> Task :geode-connectors:checkMissedTests
>> Task :geode-connectors:spotlessJava UP-TO-DATE
>> Task :geode-connectors:spotlessJavaCheck UP-TO-DATE
>> Task :geode-connectors:spotlessCheck UP-TO-DATE
>> Task :geode-connectors:test
>> Task :geode-core:assemble
>> Task :geode-core:checkMissedTests
>> Task :geode-core:spotlessJava
>> Task :geode-core:spotlessJavaCheck
>> Task :geode-core:spotlessCheck
>> Task :geode-core:test
>> Task :geode-cq:assemble
> 
>> Task :geode-cq:compileTestJava
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> 
>> Task :geode-cq:processTestResources
>> Task :geode-cq:testClasses
>> Task :geode-cq:checkMissedTests
>> Task :geode-cq:spotlessJava UP-TO-DATE
>> Task :geode-cq:spotlessJavaCheck UP-TO-DATE
>> Task :geode-cq:spotlessCheck UP-TO-DATE
>> Task :geode-cq:test
>> Task :geode-experimental-driver:jar
>> Task :geode-experimental-driver:javadoc FROM-CACHE
>> Task :geode-experimental-driver:javadocJar
>> Task :geode-experimental-driver:sourcesJar
>> Task :geode-experimental-driver:signArchives SKIPPED
>> Task :geode-experimental-driver:assemble
> 
>> Task :geode-experimental-driver:compileTestJava
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> 
>> Task :geode-experimental-driver:processTestResources
>> Task :geode-experimental-driver:testClasses
>> Task :geode-experimental-driver:checkMissedTests
>> Task :geode-experimental-driver:spotlessJava UP-TO-DATE
>> Task :geode-experimental-driver:spotlessJavaCheck UP-TO-DATE
>> Task :geode-experimental-driver:spotlessCheck UP-TO-DATE
>> Task :geode-experimental-driver:test
>> Task :geode-json:assemble
>> Task :geode-json:compileTestJava NO-SOURCE
>> Task :geode-json:processTestResources
>> Task :geode-json:testClasses
>> Task :geode-json:checkMissedTests NO-SOURCE
>> Task :geode-json:spotlessJava UP-TO-DATE
>> Task :geode-json:spotlessJavaCheck UP-TO-DATE
>> Task :geode-json:spotlessCheck UP-TO-DATE
>> Task :geode-json:test NO-SOURCE
>> Task :geode-old-versions:javadoc NO-SOURCE
>> Task :geode-junit:javadoc
>> Task :geode-junit:javadocJar
>> Task :geode-junit:sourcesJar
>> Task :geode-junit:signArchives SKIPPED
>> Task :geode-junit:assemble
>> Task :geode-junit:compileTestJava FROM-CACHE
>> Task :geode-junit:processTestResources
>> Task :geode-junit:testClasses
>> Task :geode-junit:checkMissedTests
>> Task :geode-junit:spotlessJava UP-TO-DATE
>> Task :geode-junit:spotlessJavaCheck UP-TO-DATE
>> Task :geode-junit:spotlessCheck UP-TO-DATE
>> Task :geode-junit:test
>> Task :geode-lucene:assemble
> 
>> Task :geode-lucene:compileTestJava
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> 
>> Task :geode-lucene:processTestResources
>> Task :geode-lucene:testClasses
>> Task :geode-lucene:checkMissedTests
>> Task :geode-lucene:spotlessJava UP-TO-DATE
>> Task :geode-lucene:spotlessJavaCheck UP-TO-DATE
>> Task :geode-lucene:spotlessCheck UP-TO-DATE
>> Task :geode-lucene:test
>> Task :geode-old-client-support:assemble
>> Task :geode-old-client-support:compileTestJava
>> Task :geode-old-client-support:processTestResources NO-SOURCE
>> Task :geode-old-client-support:testClasses
>> Task :geode-old-client-support:checkMissedTests
>> Task :geode-old-client-support:spotlessJava UP-TO-DATE
>> Task :geode-old-client-support:spotlessJavaCheck UP-TO-DATE
>> Task :geode-old-client-s

Build failed in Jenkins: Geode-nightly #1238

2018-06-27 Thread Apache Jenkins Server 
See 


Changes:

[github] GEODE-5346: Fix race in LauncherLifecycleCommandsDUnitTest (#2080)

[bschuchardt] GEODE-1198 CI Failure: 
DistributedSystemDUnitTest.testConflictingUDPPort

--
[...truncated 29.24 KB...]

> Task :geode-connectors:compileTestJava
Note: 

 uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-connectors:processTestResources
> Task :geode-connectors:testClasses
> Task :geode-connectors:checkMissedTests
> Task :geode-connectors:spotlessJava UP-TO-DATE
> Task :geode-connectors:spotlessJavaCheck UP-TO-DATE
> Task :geode-connectors:spotlessCheck UP-TO-DATE
> Task :geode-connectors:test
> Task :geode-core:assemble
> Task :geode-core:checkMissedTests
> Task :geode-core:spotlessJava
> Task :geode-core:spotlessJavaCheck
> Task :geode-core:spotlessCheck
> Task :geode-core:test
> Task :geode-cq:assemble

> Task :geode-cq:compileTestJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-cq:processTestResources
> Task :geode-cq:testClasses
> Task :geode-cq:checkMissedTests
> Task :geode-cq:spotlessJava UP-TO-DATE
> Task :geode-cq:spotlessJavaCheck UP-TO-DATE
> Task :geode-cq:spotlessCheck UP-TO-DATE
> Task :geode-cq:test
> Task :geode-experimental-driver:jar
> Task :geode-experimental-driver:javadoc FROM-CACHE
> Task :geode-experimental-driver:javadocJar
> Task :geode-experimental-driver:sourcesJar
> Task :geode-experimental-driver:signArchives SKIPPED
> Task :geode-experimental-driver:assemble

> Task :geode-experimental-driver:compileTestJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-experimental-driver:processTestResources
> Task :geode-experimental-driver:testClasses
> Task :geode-experimental-driver:checkMissedTests
> Task :geode-experimental-driver:spotlessJava UP-TO-DATE
> Task :geode-experimental-driver:spotlessJavaCheck UP-TO-DATE
> Task :geode-experimental-driver:spotlessCheck UP-TO-DATE
> Task :geode-experimental-driver:test
> Task :geode-json:assemble
> Task :geode-json:compileTestJava NO-SOURCE
> Task :geode-json:processTestResources
> Task :geode-json:testClasses
> Task :geode-json:checkMissedTests NO-SOURCE
> Task :geode-json:spotlessJava UP-TO-DATE
> Task :geode-json:spotlessJavaCheck UP-TO-DATE
> Task :geode-json:spotlessCheck UP-TO-DATE
> Task :geode-json:test NO-SOURCE
> Task :geode-old-versions:javadoc NO-SOURCE
> Task :geode-junit:javadoc
> Task :geode-junit:javadocJar
> Task :geode-junit:sourcesJar
> Task :geode-junit:signArchives SKIPPED
> Task :geode-junit:assemble
> Task :geode-junit:compileTestJava FROM-CACHE
> Task :geode-junit:processTestResources
> Task :geode-junit:testClasses
> Task :geode-junit:checkMissedTests
> Task :geode-junit:spotlessJava UP-TO-DATE
> Task :geode-junit:spotlessJavaCheck UP-TO-DATE
> Task :geode-junit:spotlessCheck UP-TO-DATE
> Task :geode-junit:test
> Task :geode-lucene:assemble

> Task :geode-lucene:compileTestJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

> Task :geode-lucene:processTestResources
> Task :geode-lucene:testClasses
> Task :geode-lucene:checkMissedTests
> Task :geode-lucene:spotlessJava UP-TO-DATE
> Task :geode-lucene:spotlessJavaCheck UP-TO-DATE
> Task :geode-lucene:spotlessCheck UP-TO-DATE
> Task :geode-lucene:test
> Task :geode-old-client-support:assemble
> Task :geode-old-client-support:compileTestJava
> Task :geode-old-client-support:processTestResources NO-SOURCE
> Task :geode-old-client-support:testClasses
> Task :geode-old-client-support:checkMissedTests
> Task :geode-old-client-support:spotlessJava UP-TO-DATE
> Task :geode-old-client-support:spotlessJavaCheck UP-TO-DATE
> Task :geode-old-client-support:spotlessCheck UP-TO-DATE
> Task :geode-old-client-support:test
> Task :geode-old-versions:javadocJar
> Task :geode-old-versions:sourcesJar
> Task :geode-old-versions:signArchives SKIPPED
> Task :geode-old-versions:assemble
> Task :geode-old-versions:compileTestJava NO-SOURCE
> Task :geode-old-versions:processTestResources NO-SOURCE
> Task :geode-old-versions:testClasses UP-TO-DATE
> Task :geode-old-versions:checkMissedTests NO-SOURCE
> Task :geode-old-versions:spotlessJava UP-TO-DATE
> Task :geode-old-versions:spotlessJavaCheck UP-TO-DATE
> Task

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #961 was SUCCESSFUL (with 2423 tests)

2018-06-27 Thread Spring CI 

---
Spring Data GemFire > Nightly-ApacheGeode > #961 was successful.
---
Scheduled
2425 tests in total.

https://build.spring.io/browse/SGF-NAG-961/





--
This message is automatically generated by Atlassian Bamboo

Geode unit tests completed in 'develop/DistributedTest' with non-zero exit code

2018-06-27 Thread apachegeodeci 
Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/83

Re: DISCUSS: Refactor test source set for integrationTest and distributedTest

2018-06-27 Thread Kirk Lund 
Don't forget to add "acceptanceTest/"

On Tue, Jun 26, 2018 at 3:36 PM, Jacob Barrett  wrote:

> I'd like to suggest that we refactor our current test source set, which
> contains both unit, integration and distributed tests, into distinct source
> sets, test, integrationTest, distributedTest. These source sets would
> replace the use of the primary categories UnitTest, IntegrationTest and
> DistributedTest.
>
> The catalyst for this change is an issue that Gradle's test runner doesn't
> pre-filter categories when launching tests, so if the tests are launched in
> separate JVMs or Docker containers, like :distributeTest task, the cost of
> spinning up those resources is realized only to immediately exit without
> running any test for all test classes in the module. Switching to separate
> source sets for each category would remove the need to filter on category
> and only tests in the corresponding source set would get executed in their
> external JVM or Docker container. An example of this issue is
> geode-junit:distributedTest task, which forks all test classes in separate
> JVMs but never actually runs any tests since there are no DistributedTest
> tagged tests.
>
> The secondary effect is a way too isolate dependencies in each of the
> source sets. Unit tests in the test set would not have dependencies need
> for integration tests or distributed test so that if you accidentally tried
> to import classes from those frameworks you would get a compiler failure.
> Likewise, integration tests would not include distributed test framework
> dependencies. Any shared test classes like mock, dummies, fakes, etc. could
> be shared in a commonTest source set, but would not contain any tests
> itself.
>
> The proposed structure would look like this:
>
> test/ - only contains unit tests.
> integrationTest/ - only contains integration style tests.
> distributedTest/ - only includes DUnit based tests.
> commonTest/ - includes commonly shared classes between each test category.
> Does not contain any classes.
>
> Thoughts?
>
> -Jake
>

Re: DISCUSS: Refactor test source set for integrationTest and distributedTest

2018-06-27 Thread Dale Emery 
The two main ways to organize tests are hierarchies (such as packages or file 
folders) and tagging (such as tagging).

Each supports different purposes for selecting tests to run.

Hierarchies are good for stable, mutually exclusive purposes. Unit, 
Distributed, Integration, and Acceptance seem like pretty stable purposes for 
selecting tests. Another probably stable purpose is functional area, like when 
you want to run all of the tests for a particular area.

Those two stable purposes are orthogonal, which leads to somewhat replicated 
hierarchies: Each functional area has its own unit, distributed, integration, 
and acceptance tests, or vice versa. As long as the purposes really are stable, 
this replicated structure works just fine. If they’re not stable, it’s better 
(in the absence of Gradle doing unfortunate things when it finds and filters 
tests) to use tagging for the less-stable idea.

Tagging is good when you want to select tests *across* those more stable 
purposes, or *within* them. I don’t know enough about GemFire/Geode to know 
what things might be best represented by tags.

The key, I think, is to figure out which purposes are more stable, and use 
hierarchies to organize tests for those purposes, then use tagging for 
crosscutting or ad hoc selection.

—
Dale Emery
dem...@pivotal.io

> On Jun 26, 2018, at 4:34 PM, Patrick Rhomberg  wrote:
> 
> I like the idea of good structure around our test-complexity @Category
> layout.
> 
> @Alexander, not to speak for Bruce, but to my mind things like SecurityTest
> / WanTest / etc are orthogonal to the UnitTest / IntegrationTest /
> DistributedTest / AcceptanceTest classification.  I like adding better
> runtime and structure on the latter, but there's no real reason to
> sacrifice the former labeling.
> 
> @Anthony, I'm pretty confident we'll need a commonTest.  Off the top of my
> head, it'll need to host the startup rules, GfshRule, and the
> SimpleSecurityManager.
> 
> On Tue, Jun 26, 2018 at 4:22 PM, Anthony Baker  wrote:
> 
>> Sounds good, though I’m not entirely sure we need ‘commonTest/‘.  I guess
>> we’ll find out :-)
>> 
>> Anthony
>> 
>> 
>>> On Jun 26, 2018, at 4:19 PM, Dan Smith  wrote:
>>> 
>>> +1 for the suggested structure.
>>> 
>>> -Dan
>>> 
>>> On Tue, Jun 26, 2018 at 3:36 PM, Jacob Barrett 
>> wrote:
>>> 
 I'd like to suggest that we refactor our current test source set, which
 contains both unit, integration and distributed tests, into distinct
>> source
 sets, test, integrationTest, distributedTest. These source sets would
 replace the use of the primary categories UnitTest, IntegrationTest and
 DistributedTest.
 
 The catalyst for this change is an issue that Gradle's test runner
>> doesn't
 pre-filter categories when launching tests, so if the tests are
>> launched in
 separate JVMs or Docker containers, like :distributeTest task, the cost
>> of
 spinning up those resources is realized only to immediately exit without
 running any test for all test classes in the module. Switching to
>> separate
 source sets for each category would remove the need to filter on
>> category
 and only tests in the corresponding source set would get executed in
>> their
 external JVM or Docker container. An example of this issue is
 geode-junit:distributedTest task, which forks all test classes in
>> separate
 JVMs but never actually runs any tests since there are no
>> DistributedTest
 tagged tests.
 
 The secondary effect is a way too isolate dependencies in each of the
 source sets. Unit tests in the test set would not have dependencies need
 for integration tests or distributed test so that if you accidentally
>> tried
 to import classes from those frameworks you would get a compiler
>> failure.
 Likewise, integration tests would not include distributed test framework
 dependencies. Any shared test classes like mock, dummies, fakes, etc.
>> could
 be shared in a commonTest source set, but would not contain any tests
 itself.
 
 The proposed structure would look like this:
 
 test/ - only contains unit tests.
 integrationTest/ - only contains integration style tests.
 distributedTest/ - only includes DUnit based tests.
 commonTest/ - includes commonly shared classes between each test
>> category.
 Does not contain any classes.
 
 Thoughts?
 
 -Jake
 
>> 
>>

Re: DISCUSS: Refactor test source set for integrationTest and distributedTest

2018-06-27 Thread Darrel Schneider 
what about "testUtilities" instead of "commonTest"?

On Tue, Jun 26, 2018 at 3:36 PM, Jacob Barrett  wrote:

> I'd like to suggest that we refactor our current test source set, which
> contains both unit, integration and distributed tests, into distinct source
> sets, test, integrationTest, distributedTest. These source sets would
> replace the use of the primary categories UnitTest, IntegrationTest and
> DistributedTest.
>
> The catalyst for this change is an issue that Gradle's test runner doesn't
> pre-filter categories when launching tests, so if the tests are launched in
> separate JVMs or Docker containers, like :distributeTest task, the cost of
> spinning up those resources is realized only to immediately exit without
> running any test for all test classes in the module. Switching to separate
> source sets for each category would remove the need to filter on category
> and only tests in the corresponding source set would get executed in their
> external JVM or Docker container. An example of this issue is
> geode-junit:distributedTest task, which forks all test classes in separate
> JVMs but never actually runs any tests since there are no DistributedTest
> tagged tests.
>
> The secondary effect is a way too isolate dependencies in each of the
> source sets. Unit tests in the test set would not have dependencies need
> for integration tests or distributed test so that if you accidentally tried
> to import classes from those frameworks you would get a compiler failure.
> Likewise, integration tests would not include distributed test framework
> dependencies. Any shared test classes like mock, dummies, fakes, etc. could
> be shared in a commonTest source set, but would not contain any tests
> itself.
>
> The proposed structure would look like this:
>
> test/ - only contains unit tests.
> integrationTest/ - only contains integration style tests.
> distributedTest/ - only includes DUnit based tests.
> commonTest/ - includes commonly shared classes between each test category.
> Does not contain any classes.
>
> Thoughts?
>
> -Jake
>