Testing

Drizzle Testing Outline

The current testing framework MySQL uses is too monolithic containing about 15 test files which makes the using, creating and debugging of drizzle tests very challenging. Essentially if creating tests is too hard, it won't get done.

The goals of the drizzle testing framework:

• Replace monolithic testing with a more granular approach.
• Tests need to emit Test Anything Protocol (TAP).
• Single test result analyzer supporting TAP output.
• Granualar testing process: input->client->server->client->output
• libdrizzle-API testing
• protocol-level testing

libdrizzle-API Testing

API tests for libdrizzle.

Protocol Testing

Simulation of what libdrizzle is supposed to be doing according to the spec.

Implementation

Refactor current tests in t directory.

Note: Vagueness is intentional right now. Details to come.