Improve tests performance

[jerstlouis]

Is your feature request related to a problem? Please describe.
Executing the tests on our implementation takes a good 30 minutes even when testing only 3 collections.
I don't think it is because of processing or data transfer time on our end. It is also a lot more time than the sum of the duration of the tests, most of which are under 1s except for 4 that take up to ~1min30s. Opened a separate issue (#182) about the lack of progress indicator during that time, which originally had me think the tests were stuck.

Describe the solution you'd like
The tests should complete relatively quickly, in about the amount currently reported in the test report.

[dstenger]

Thank you for reporting.

This problem is most likely related to the number of features provided by the collections.

[jerstlouis]

Thank you @dstenger .
I believe the test uses the first 3 listed vector collections on our server which are:

NaturalEarth:cultural:ne_10m_admin_0_boundary_lines_maritime_indicator (220 features, items: 236kb)
NaturalEarth:cultural:ne_10m_admin_0_antarctic_claims (10 features, items: 462kb)
NaturalEarth:cultural:ne_10m_admin_0_sovereignty (206 features, items: 20.8 mb, response+download time for all 206 features is ~40s)

I wouldn't consider this a large number of features -- we are planning to eventually host the full 60+GB Planet OpenStreetMap dataset which has over a billion features.

Ideally the tests should work without requesting every single feature and/or otherwise allow the user to explicitly list collections of a reasonable size to test.

The issue might be processing the sovereignty as it contains a significant bit of geometry. This highlights the importance of a geometry simplification / clipping capability.

Regardless, the current responses should be manageable in a lot less time.

[dstenger]

@jerstlouis We cannot reproduce the test run of 30 minutes anymore. However, we agree that the performance can be improved. Issue #202 was created to improve the performance of the test suite.
If you agree, I propose to close this issue.

[jerstlouis]

Thanks @dstenger . Closing. I will reopen with more details if I run into a similar 30 minutes wait again.

What would be really great is to have a continuously updating log visible to the user in the client window of which requests are being sent to the server.