Reference Transfer: transfers the reference of the first hit in the search response to the Details request.Sample Text Search: performs a text-based query on “restaurants in Sydney”.Details: Gets the details of the reference and validates that it has the same coordinates as in the nearbysearch result.Reference Transfer: Transfers the reference of the first hit in the nearby search result to the Details request.Nearby Search Sample: Performs a nearby search with given coordinates.Similarly, the Places API TestSuite contains one TestCase for each of these API resources: The Places API Rest Service defines a number of resources with contained GET methods and sample requests. The places API is the only API in this sample that requires an API Key – see below on how that is configured in the project. Component Filtering only Sample: performs an lookup with only a component filter and validates the returned geometry.Component Filtering Sample: performs an address lookup with a component filter and validates the returned geometry.Region Biasing Sample: performs an address lookup with constraining region and validates the returned geometry.Viewport Biasing Sample: performs an address lookup with constraining bounds and validates the returned geometry.Reverse Lookup Sample: performs a reverse lookup (by specifying coordinates) and verifies the geometry in the result.Sample Request: validates the geometry coordinates in JSON format of a specified address.The GeoCoding API TestCase contains a number of lookup requests: Path Elevation Sample: specifies a path in coordinates and validates the response to contain the correct elevations.Sample Request – Multiple Responses: specifies multiple coordinates and validates the response to contain corresponding elevations.Sample Request: specifies coordinates and validates the response to contain the correct elevation.The TestCase performs the following steps: The sample requests for the Elevation API are equally straight forward: The request retrieves a distance matrix for a number of destination and origin locations and validates the returned destination/origin addresses and the size of the returned matrix. The Distance Matrix API Rest Service and corresponding TestCase contains a sample request for a distance matrix request: Transit with departure time: Looks up a transit from Brooklyn to Queens from the current time and validates the start/end locations and the number of required steps in the XML response.Sample Request – no highways: Gets the same directions without highways, validates the number of steps (281!) and bounding coordinates.Sample Request : Gets directions from Toronto to Montreal in JSON format and validates the number of steps and bounding coordinates.
The Direction API Rest Service and corresponding TestCase contain requests for basic direction lookups: Let’s look at each of the APIs and their TestCase(s) in turn.
GOOGLE EARTH JSON QUERY UPDATE
Many of the Assertions in the project are used to validate response content containing coordinates, for example:Īs you can see the validation is up to 7 decimals, unfortunately though the last decimals of returned coordinates change rather frequently in which case you will have to either update the “Expected Result” value of the assertion to be in line with the current value, or change the assertion alltogether to either ignore coordinates or handle changes (for example by selecting specific values and truncating them). The “Master TestSuite” at the end shows how one can have more fine-grained control over the execution of other Tests (see below). The overall structure of the project is as follows:Īs you can see the core APIs have been defined as separate REST Services in the project and there is one TestSuite corresponding to each API.
The sample project for the Google Maps defines a number of requests for each of the APIs exposed by Google Maps.
0 kommentar(er)
