Increase testing of dump and restore
Increase testing of basic dump and restore functionality with the random query generator
Blueprint information
- Status:
- Complete
- Approver:
- Brian Aker
- Priority:
- Medium
- Drafter:
- Patrick Crews
- Direction:
- Approved
- Assignee:
- Patrick Crews
- Definition:
- Approved
- Series goal:
- Accepted for dexter
- Implementation:
- Implemented
- Milestone target:
- 2010-08-16
- Started by
- Patrick Crews
- Completed by
- Patrick Crews
Related branches
Related bugs
Sprints
Whiteboard
This blueprint will cover testing of dump + restore functionality with both the randgen and the regular test suite.
Randgen testing will involve creating subsets of various tables, dumping them, restoring them, then comparing against the original. We will add the randgen tests to our automated systems once it is ready.
A similar approach will be used with the test suite (noted below).
Added a testcase for the basic test suite:
https:/
This is a port from MySQL that does basic testing of dumping a table, restoring it, and comparing it to the original.
Our test now randomly generates test tables based on an initial test-bed. The population and composition is randomly-determined (either via straight INSERTs or CREATE'ing a new table via joins of existing ones).
We populate the test database with varying numbers of tables per cycle of the randgen.
At the end of each cycle, we dump the test DB, restore the tables to a new DB, then do table-table compares for restored and original tables.