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

[TEST] support stashed values within property names in our REST tests #9533

Merged
merged 2 commits into from Feb 3, 2015

Conversation

javanna
Copy link
Member

@javanna javanna commented Feb 2, 2015

Support stashed values within property names, feature that was added to the REST spec in e7ac5f2 .

@javanna javanna added >test Issues or PRs that are addressing/adding tests review v1.5.0 v2.0.0-beta1 labels Feb 2, 2015
@@ -246,6 +243,7 @@ public static void runUpgrade(HttpRequestBuilder httpClient, String index, Strin
assertEquals(200, rsp.getStatusCode());
}

@SuppressWarnings("unchecked")
Copy link
Member

Choose a reason for hiding this comment

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

While the changes to this file seem fine, I don't understand what they have to do with this PR?

Copy link
Member Author

Choose a reason for hiding this comment

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

nothing....just that I went over this class because it used JsonPath#evaluate which I was changing and then I went wild on fixing compiler warnings.... can revert :)

Copy link
Contributor

Choose a reason for hiding this comment

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

it's perfectly fine to clean these things up as we go... I don't see a need to have separate PRs for these small cleanups

Copy link
Member

Choose a reason for hiding this comment

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

I don't have a problem with the change. I was trying to understand why it was here.

@jpountz
Copy link
Contributor

jpountz commented Feb 3, 2015

LGTM

…object

We had a REST test that relied on matching a json response against a regex. It worked but the match wasn't done against the actual json object, but its java map representation converted into a string by calling `toString`. Since all other clients test runners don't work in this case, as they try to match a json object against a regex, we should do the same and prevent it from working.
@javanna javanna merged commit 0e67dda into elastic:master Feb 3, 2015
@javanna javanna removed the review label Feb 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>test Issues or PRs that are addressing/adding tests v1.5.0 v2.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants