Allow for testing migration logic of our Actors
Currently there is no way for the testing library to (gracefully) abort a run, evaluate its aborted state. And then resurrect the run and evaluate the final state of the Actor. This feature would allow us to test that migration logic within the Actor is set up correctly and all of the internal state survives migration.
Example
In e-commerce scraping tool we have several counters that keep track of returned results. If one of these counters isn't properly saved into KV store a migration will cause the counter to reset and for the Actor to return more results than requested.
Allow for testing migration logic of our Actors
Currently there is no way for the testing library to (gracefully) abort a run, evaluate its aborted state. And then resurrect the run and evaluate the final state of the Actor. This feature would allow us to test that migration logic within the Actor is set up correctly and all of the internal state survives migration.
Example
In e-commerce scraping tool we have several counters that keep track of returned results. If one of these counters isn't properly saved into KV store a migration will cause the counter to reset and for the Actor to return more results than requested.