TestMultipleRangeWithoutContentLengthServer

[Martin Pool]

In test_http, TestMultipleRangeWithoutContentLengthServer calls MultipleRangeWithoutContentLengthServer which will raise a NameError, and yet the test still passes. See https://code.edge.launchpad.net/~mbp/bzr/597791-http-tests/+merge/37941

[Vincent Ladeuil (vila)]

There are multiple layers involved when it comes to decide how readv() requests are mapped to http range requests.

In this precise case, the server code that is expected to execute is just never reached by the corresponding tests because the readv requests are turned into encompassing single range requests.

There is a basic flaw in the http tests design: they insist of testing public transport methods leading to tests that are almost blackbox ones and this an example of why it's a bad design.

For these specific tests I suggest to go deeper in the API calls to be just above the http multi range requests building.