Guaranteed timeouts for loss/corruption tests

[anrossi]

We've noticed several instances where the corruption or loss tests will timeout because the packets containing ACKs will all be discarded. Or the retransmit timeouts exceed the app's timeout. We could keep increasing the interop app's timeout, but that's no guarantee the test will complete within that time.
One such instance where the app's timeout fired after 25 seconds is here
Here's an instance where the test couldn't have succeeded due to too much loss. See file download spvheipeue
Solution proposal:
It would be beneficial to have QNS be able to guarantee that the test should complete before a given timeout, and that it could provide this expected timeout to the applications. Alternatively, if QNS could deem a non-passable scenario (i.e. when it drops all ACKs and disconnect timeout occurs) as a test pass, instead of failure, that would also be beneficial.