[automated-testing] gluster-block: Discussion regarding glusto tests

Nigel Babu nigelb at redhat.com
Mon Jul 2 07:09:42 UTC 2018

Removing the extraneous CC and moving this to automated-testing@

I'm going to split this into two questions. About libraries and tests. For
* Do you use any of the libraries in glusto-tests?
* Do you have any new libraries that will be consumed by the existing tests
in glusto-tests or a library inside glusto-tests?

If your answer is yes to any of those, you should move your libraries to
glusto-tests. If the answer is no, you can safely use your own repo for

Now about tests. The argument that developers can test their changes
locally doesn't hold water. You can test your changes locally either way. I
will consider the argument that you can version your tests to match the
version of your code, however. That's a valid reason.

There is a tradeoff. You may want to run tests against an older version of
the repo or a fork of the repo (for example an internal repo), how do you
plan on doing that? Copy the tests to the internal repo too? What happens
if you've developed a newer test upstream which you want to test against an
older version downstream during a feature freeze?

On Mon, Jul 2, 2018 at 11:46 AM Bhumika Goyal <bgoyal at redhat.com> wrote:

> Hi all,
> During stop-gap, we wrote some libraries(patch on gerrit) and test
> cases(PR on gluster-block repo currently) for gluster-block using glusto.
> Some of us think that having the glusto based test cases in the
> gluster-block repo instead of glusto-tests repo would be easier for
> developers to test their changes locally. In this way, we don't have to
> deal with two repos for testing the changes every time.
> What are your suggestions and is it okay to go with this approach?
> Thanks,
> Bhumika

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/automated-testing/attachments/20180702/1d99b379/attachment.html>

More information about the automated-testing mailing list