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.

Sign up for GitHub

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

Jump to bottom

data boot strapper tests #81

Open

joe-getcouragenow opened this issue Nov 18, 2020 · 0 comments

Contributor

joe-getcouragenow commented Nov 18, 2020 •

edited

Loading

The test data bootstrapper is reasonably stable and can be used at any level of the architecture.

As we iterate on the code, we need a way to catch breaking the system. Typically it will be if the proto or DB schema changes.

How best to automate this and not create a developer burden ?

Ideas ...

Gen API Testers...

We already gen the CLI that wrps the Proto client, and the fake test data.
We can probably generate a Test Harness that calls the CLI using the generated test data.
The trick is to validate that the results are correct using goldens. This is a hard problem because the goldens have to be created. Sometimes you can use the previous git tagged ones.

https://github.com/loadimpact/k6/tree/master/samples/grpc_server

k6 looks like it has a wide gamut of things we need.
Its golang
also can use js, and so allows non devs to write tests after they have run the test dtaa bootstrapper.
seems like a good mix.
module like us: https://k6.io/docs/using-k6/modules
test metrics: https://k6.io/docs/using-k6/metrics. Def need this.
run on own cloud ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment