Our current releases are chaotic with no safety checks and depend on individual maintainers to test components independently. We want to implement nightly automated testing including sanity, functional, scenario and upgrade tests to catch issues early. To get there, we will use Glusto for basic validation and upgrade testing, dedicate resources to performance testing and scenario testing, adding new scenarios each release cycle.

1. Deterministic
Releases
Nigel Babu - nigelb@redhat.com
Principal Yak Shaver

2. Our releases now

3. Our releases now - Chaos
© william veerbeek on Flickr. CC-NC-SA

4. No safety checks

5. Chaotic
No safety checks
Depends on maintainers
Components are tested
independently
Our releases now

6. Where we want to be
Nightly automated tests
Sanity tests
Does Gluster install and run correctly?
Functional tests
Does this code do what it’s supposed to do?
Scenario tests
How does Gluster perform for this use case?
Upgrade tests
What happens when I upgrade to this version?
Do all of the above work out okay?

7. © lindsayensing on Flickr. CC-BY

8. How do we get there?
Glusto
QE team is committed to upstream-first BVT tests
We can use this to power a lite upgrade testing
Performance Testing
Catch regressions early
Dedicate energy to reducing bottlenecks
Scenario Testing
We come up with scenarios where we currently claim
to do well.
Add scenarios every cycle.