ROCK builds quickly, than it gets tested (not as quickly).
Currently, the extensive scope of features and flexible deployment options in the ROCK stack + the highly automated build cycle has led us to a situation where evaluating a release candidate’s readiness is a frequent set of tasks in need of some definition, support, and ultimately automation where possible.
This topic can serve as a place to:
- outline the objectives of RC testing
- identify a quickly implemented, iterable method to evaluate release worthiness
- develop a method to recognize QA contributors (because even in the unlikely event we automate this entirely, somebody has to analyze the results)