[automated-testing] [Gluster-Maintainers] seeking an update on the plans around automated tests and test framework for Gluster

[Amar Tumballi]

Hi Sankarshan, and others,

Some updates inline.

On Tue, Feb 4, 2020 at 12:11 PM sankarshan <sankarshan at kadalu.io> wrote:

> This is a good set of updates. If we wanted to discuss the impact of
> this activity in terms of how they have been improving the user
> experience for (a) specific workflows or, (b) specific workloads - how
> can we measure the robustness of the current test library (or, batches
> of tests) in Glusto? I'd like to see a conversation - perhaps at an
> upcoming Community Meeting - from this perspective. The kind of
> workloads for which Gluster is used is more or less well known by now.
> So, being able to validate the readiness and extensive consumption of
> Glusto tests from that perspective would be good to see.
>
>
Agree! I do see a lot of activity on Glusto-tests repository, but doesn't
see where to find the run, or the result of the run. Also, haven't seen any
bugs/issues raised from the testing using glusto.  While the number of
patches is great, the value we need is surely through the ability to find
use-case specific bugs which we couldn't test through regression framework
in glusterfs repository.


> On Tue, 4 Feb 2020 at 11:47, Bala Konda Reddy Mekala <bmekala at redhat.com>
> wrote:
> >
> > Hi Sankarshan,
> > Glusto as a framework is definitely matured and glusto-tests
> > where it is closely related to Glusterfs.
> > Enhancements to glusto-tests is an on-going process.
> >
> > Below are the details of work being done in the last three months.
> >
> > Currently glusto tests is compatible with python 3 a total
> > of 28 PR's were sent [1]
> > A total of 58 PR's were merged among them 20+
> > were the new test cases and the rest are library fixes. [2]
> > Libraries for geo-rep and brick-mux are in review.
> > Optimization of existing code for reducing test time
> > is being carried out and the few patches were merged
> >  NFS Ganesha tests were tested and merged as part of
> > glusto-tests.
> > Now User can run the tests using tox.
> > New test cases and library fixes are being sent and are in
> > review. [3]
> >
> > Regards,
> > Bala
> > [1]
> https://review.gluster.org/#/q/status:merged+project:glusto-tests+topic:py2to3
> [2] https://review.gluster.org/#/q/status:merged+project:glusto-tests,75
> > [3]https://review.gluster.org/#/q/project:glusto-tests++status:open
> >
> >
> > On Mon, Feb 3, 2020 at 9:40 PM sankarshan <sankarshan at kadalu.io> wrote:
> >>
> >> I have not seen any meaningful updates about the automated tests and
> >> testing framework in the recent times. I'd like to understand whether
> >> forward looking plans towards enhancements and sustaining a viable
> >> test framework (in this case, Glusto) have been discussed?
> >>
> >> I'd like to understand whether the Glusto framework has evolved and
> >> matured over the period of time it has been part of Gluster and the
> >> maintenance lifecycle and governance around the project.
> >>
> >> /s
>
>
While it is not directly related, Aravinda did propose a testing framework
<https://kadalu.io/rfcs/0002-test-framework-binnacle.html> called Binnacle
<https://github.com/kadalu/binnacle> (a project to test kadalu.io), which
by design can also in future work for glusterfs testing too. As we don't
have anything more than proposal yet on binnacle, wouldn't be good to say
this is ready to be considered alternative, our idea is, through binnacle,
we can test **any** distributed project. Would be good for people to keep a
watch!

-Amar


> --
> sankarshan at kadalu.io | TZ: UTC+0530
> kadalu.io : Making it easy to provision storage in k8s!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/automated-testing/attachments/20200205/2eb70a8d/attachment.html>