Test Runs and Cycles

Complex systems can be “eventually consistent,” meaning there is no way to get a static, consistent snapshot of its state when it's running normally. This impedes verifying that everything in the system is in the state it should be. The solution is to stop all activity every given amount of time and then evaluate the system. This run, stop, run behavior is called “running in cycles.” This also provides the chance to “clean up” the test platform, deleting erased table rows and the like.