[Gluster-devel] Identifying tests to automate with Glusto

Nigel Babu nigelb at redhat.com
Mon Oct 30 15:24:15 UTC 2017

>> One of the missing part with existing .t tests in glusterd is the client
>> and server compatibility with different op-versions. Off late we have seen
>> most of the bugs. I think we’d need to write tests with clients running
>> with different versions, heterogeneous servers ( in n to n-2 range for both
>> client and server) and ofcourse the upgrade tests.
> Let me extend this thought. We need the compatibility tests run across all
> options that are supported and such, so that we know what breaks, a very
> generic compat test against an older client is not sufficient.
> IOW, test every option documented (and possibly not documented) in the
> upgrade and compat tests across servers and clients.
> As we hear more about large clusters, or client count explosion, we need
> to ensure we break nothing and can certify the same for every release.

I don't disagree, but let's keep this discussion focused on specific tests
and failure scenarios. Preferably, one where you can write out what needs
to be tested in words and Kartik can help code/automate that.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20171030/e3290f4a/attachment.html>

More information about the Gluster-devel mailing list