This has been a long withstanding issue that keeps coming up in the pipeline every once and awhile (due to changes on the Service end). For the time being, the test only does the following:

• Test that the Service accepts our SQL-like query
• Test that our SQL-like query is well-formatted and does not return an exception

We would like to eventually extend the test to also do the following:

• Verify the output matches the expected output. Due to changes in the Service end, byte-by-byte comparison has proven problematic. To alleviate this, we should probably get a better understanding of what this API call does so that we can compare the properties of the output rather than byte by byte (as any difference may just be due to formatting of the output, not an actual difference in the data being communicated).