The test did not synchronize the slaves before doing a read that depended on replication being in sync. It also didn't clear the previous value from the buffer used to store the test form results which caused a misleading error message.
The test now checks that text protocol prepared statements are load balanced just like normal queries.
