The astrolabe project currently tests various Atlas planned maintenance scenarios in an attempt to find problematic scenarios indicating either driver bugs or bugs in the planned maintenance scenarios themselves. So far the project has not found bugs in either (aside from timeout issues in cloud-dev).

We need to test Astrolabe itself to see if it actually achieves its goals. One way to do this would be to test a driver version that is known to have bugs related to planned maintenance, along with the workload that was used to reproduce the bug, and see if those bugs are reproduced by Astrolabe. We would want to continually test Astrolabe this way to ensure future changes to it don't obscure known driver bugs. As new driver bugs are found the pre-bugfix version of the driver, and the workload that reproduces the bug, should be added to a corpus of such tests.