Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test automation -- Beyond 6.1 #2

Open
onderkalaci opened this issue Dec 15, 2016 · 1 comment
Open

Test automation -- Beyond 6.1 #2

onderkalaci opened this issue Dec 15, 2016 · 1 comment

Comments

@onderkalaci
Copy link
Member

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)
@lithp
Copy link
Contributor

lithp commented Jan 11, 2017

For the 3rd one, you now have the pg.stop task and friends.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants