Yup. We consider tests to tbe first class citizen, but aren't distribute them as such.
@Jay: hacking is great and all that. My point is different: tests should be fixed at the point of the release (and they are); but there's no way to run them easily against an installed cluster, unless you clone the workspace and checkout the correct tag. Which isn't very user-friendly. Cos On Sun, Feb 08, 2015 at 04:54PM, Roman Shaposhnik wrote: > Are you taking about packaging them as a standalone self-contained > RPM/DEB package? > > Thanks, > Roman. > > On Sun, Feb 8, 2015 at 3:35 PM, Konstantin Boudnik <[email protected]> wrote: > > It might have been discussed before, but I can not find any traces of such > > discussion. So... > > > > what do you people think of packaging of the cluster tests as a part of a > > stack? We have a good start in the form of light-weight fast tests; now they > > can be packaged and delivered as a part of the normal release. So, one a > > cluster is deployed it'd be easy to quickly run a validation of it using the > > same set of workloads that was used for the release itself. > > > > I think we were somewhat going in that direction with test fatjar and all, > > but > > have never gotten to the point where it was actually usable for the users, > > not > > just stack developers... > > > > Thoughts? > > -- > > Cos > >
