You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm noting some ideas for future improvements (and keep updating in the future as I think of other ideas):
Add ability to compare the data in the placements of shards. Use case for this: run a lot of concurrent modifications and then compare the placements of shards to ensure that nothing goes wrong.
Consider this framework as a new kind of regression suite. For instance, as a new feature tester in the release testing, use a very simple API and add your tests to this new regression test suite. This could enable running those tests repeatedly and use it in the future.
I don't know the methodology of this yet, just noting here not to forget.
We could very well integrate concurrency testing into this.
We should have an easy way of killing the workers in various ways (kill -9, pg_ctl stop etc)
The text was updated successfully, but these errors were encountered:
I'm noting some ideas for future improvements (and keep updating in the future as I think of other ideas):
kill -9
,pg_ctl stop
etc)The text was updated successfully, but these errors were encountered: