Re: [libvirt] [libvirt-test-API] Plans for code update

From: "Martin Kletzander" <mkletzan(a)redhat.com&gt; To: "Ruifeng Bian" <rbian(a)redhat.com&gt; Cc: libvir-list(a)redhat.com Sent: Friday, June 24, 2016 5:20:15 PM Subject: Re: [libvirt] [libvirt-test-API] Plans for code update [Cc'ing Suren as he might have some info] On Thu, Jun 23, 2016 at 10:51:34PM -0400, Ruifeng Bian wrote: > > >----- Original Message ----- >> From: "Martin Kletzander" <mkletzan(a)redhat.com&gt; >> To: "Ruifeng Bian" <rbian(a)redhat.com&gt; >> Cc: libvir-list(a)redhat.com >> Sent: Thursday, June 23, 2016 8:57:26 PM >> Subject: Re: [libvirt] [libvirt-test-API] Plans for code update >> >> On Thu, Jun 23, 2016 at 02:17:22AM -0400, Ruifeng Bian wrote: >> > >> >I am not sure how many of you keep an eye on this project. >> >> From what I know, not many. I believe it is used in some CI >> _somewhere_... by _someone_. >> >> >The project is for testing libvirt-python APIs, but many test cases are >> >not fully implemented until now. >> >> And many of them are broken by design. I remember fixing one just out >> of sheer curiosity and it was hard not to go down the rabbit hole and >> get stuck in there. >> >> >We want to keep this project updated in the future, the following aspects >> >will be considered to update the code: >> >1. Code style - Use inspekt to check code style. >> >2. Pythonizing the code - Replace all shell scripts with python. >> >3. Bug fixing - Some code bugs need to be fixed. >> >4. New features - Add more API test cases. >> > >> >> Good luck with that, it looks like the code haven't gotten a good scrub >> in years. Are you planning to use it somewhere? Will there be anything >> left after cleanups? =) > >Actually we always use this project in our team. But the code hasn't >synchronized >to upstream for a long time. We have 3 guys working on this project now. And >we >Plan to synchronize our code with upstream recently. > >> >> >Any feedback or suggestion is welcome. Let's work together to contribute >> >to this project. >> > >> >> One suggestion could be too have a look at avocado-vt (what used to be >> autotest's virt-test) for that is being still actively developed. >> Although I have no idea what's your intention, so I might be just >> generating noise, in which case I apologise. > >Yes, we also have the thought of integrating this project with avocado-vt. >It will >require much work to do. We will take this as our second step. > It shouldn't be that hard, though. I haven't had any one of them set up in a while, but if I'll find some time somewhere I'll try to look into that. The integration with avocado-vt is the only benefit I could've thought of. It would be great if we could expand the testing by fixing that test suite and integrating it into existing CI.

>Thanks a lot. > >> >> Have a nice day, >> Martin >> >> >Thanks, >> >Ruifeng Bian >> > >> >-- >> >libvir-list mailing list >> &gt;libvir-list(a)redhat.com >> >https://www.redhat.com/mailman/listinfo/libvir-list >> >> -- >> libvir-list mailing list >> libvir-list(a)redhat.com >> https://www.redhat.com/mailman/listinfo/libvir-list -- libvir-list mailing list libvir-list(a)redhat.com https://www.redhat.com/mailman/listinfo/libvir-list