The test appears to fail due to connection errors when it attempts to check whether MaxScale is still alive. To offset the chance of the backend server still refusing connections after the initial spike, the sleep before the check was increased.
