[Issue 1173] In "SendAndReceive", wait 100ms before reading

[jochenehret]

What is this change about?

Prevents race condition when sending a test message to a backend and reading the response.

Please provide contextual information.

#1173

What version of cf-deployment have you run this cf-acceptance-test change against?

v41.0.0

Please check all that apply for this PR:

• introduces a new test --- Are you sure everyone should be running this test?
• changes an existing test
• requires an update to a CATs integration-config

Did you update the README as appropriate for this change?

• YES
• N/A

If you are introducing a new acceptance test, what is your rationale for including it CATs rather than your own acceptance test suite?

How many more (or fewer) seconds of runtime will this change introduce to CATs?

Function is called 7 times -> 700ms.

What is the level of urgency for publishing this change?

• Urgent - unblocks current or future work
• Slightly Less than Urgent

Tag your pair, your PM, and/or team!

It's helpful to tag a few other folks on your team or your team alias in case we need to follow up later.

[ctlong]

Could we resolve the problem by using an Eventually when calling SendAndReceive instead? I would prefer that approach in order to allow the test to succeed faster, if possible.

[jochenehret]

Using Eventually when calling SendAndReceive could also fix the problem. But logically, I think it makes sense to add a short wait before the Read call. The tests are running on our K8s Concourse on GCP. The test apps runs on an AWS account behind a network load balancer. So the full roundtrip is expected to take a short amount of time. I would propose to wait 100ms and see how that works.