I observed the same thing -- even with an ES instance running some tests
would fail on my Mac, though I don't remember exactly which ones they were.
I also observed that running tests from gradle ran a different number than
when I ran via Eclipse, where with gradle a few of the Hadoop interfaces
were skipped. It'd be great to get the tests fixed up and better coverage,
as I'm very interested in this project as well. Sounds like you're on it,
which is awesome!

On Thu, Apr 11, 2013 at 7:27 AM, Christian Tzolov
notifications@github.comwrote:

Hi @ash211 https://github.com/ash211,

Haven't mentioned it above but I did run the tests with ES running at
localhost:9200 but they fail. Are they passing OK for you? (mind the
'clean' task in the gradlew call).

Checking CascadingHadoopTest and CascadingLocalTest reviles an incorrect
assumption that the testWriteToES() method is called before the
testReadFromES(). JUnit does not guaranty the order of execution.
I fixed this but it still fails. Seems like the testWriteToES() (in both
tests) never calls the RestClinet.create(...) method.

I will do some more digging.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-16229042
.

Broken tests #27

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions