We had no control over the other team. They were already responsible for QA of most of the system, but most of that just consisted of running existing QA test

We had no control over the other team. They were already responsible for QA of most of the system, but most of that just consisted of running existing QA test cases and reporting when they failed. As we were implementing new network protocols that they did not have existing test cases for, the work QA was responsible for was rather more complex. The issues were typically of the form "run this test script and tell us what happened for you" => "it failed" and then provided no useful information. Each step was a 24 rtt nightmare until we pushed for conference calls at 11pm local time for us. At the time we also heard of a horror tales from the offshore team. In one case a new hire had gone through the interview process, accepted the job offer, showed up for the first day, just left and never came back after a better offer came in. Suffice it to say that the offshore QA team was not exactly high quality without the ability to retain employees. It was not like the QA teams I've encountered at other jobs where QA writes a lot of their own testing infrastructure and are on an equal footing with the developers. Sadly they were more like a glorified checklist processing system, and were probably in over their heads.