Browse Source

test/ciao: fix inverted negative latitudes in tests

See https://github.com/elastic/elasticsearch/issues/18458
pull/639/head
Patrick Mezard 9 years ago
parent
commit
0f0cfd16d9
  1. 8
      test/ciao/search/boundary_rect_valid.coffee

8
test/ciao/search/boundary_rect_valid.coffee

@ -1,6 +1,6 @@
#> bounding rectangle
path: '/v1/search?text=a&boundary.rect.min_lat=-40.659&boundary.rect.max_lat=-41.614&boundary.rect.min_lon=174.612&boundary.rect.max_lon=176.333'
path: '/v1/search?text=a&boundary.rect.max_lat=-40.659&boundary.rect.min_lat=-41.614&boundary.rect.min_lon=174.612&boundary.rect.max_lon=176.333'
#? 200 ok
response.statusCode.should.be.equal 200
@ -31,7 +31,7 @@ should.not.exist json.geocoding.warnings
#? inputs
json.geocoding.query['text'].should.eql 'a'
json.geocoding.query['size'].should.eql 10
json.geocoding.query['boundary.rect.min_lat'].should.eql -40.659
json.geocoding.query['boundary.rect.max_lat'].should.eql -41.614
json.geocoding.query['boundary.rect.min_lat'].should.eql -41.614
json.geocoding.query['boundary.rect.max_lat'].should.eql -40.659
json.geocoding.query['boundary.rect.min_lon'].should.eql 174.612
json.geocoding.query['boundary.rect.max_lon'].should.eql 176.333
json.geocoding.query['boundary.rect.max_lon'].should.eql 176.333

Loading…
Cancel
Save