[yast-devel] AutoYaST Integration Tests
Hi, I have written a little test framework for running AutoYaST integration tests by using veewee, vagrant and pennyworth. I have not written something new but have only taken already existing tools and workflows. Features * Building KVM images by using AutoYaST profiles. * Checking these KVM images with rspec tests. * Generating own installation ISOs with local built RPMs or the newest one from OBS.
From my point of view it helps me to make changes in AutoYaST and running complete integration tests before submitting the package to OBS/IBS.
If you are interested please have a look to: https://github.com/schubi2/autoyast_test Greetings Stefan -- ******************************************************************************* Stefan Schubert e-mail: schubi@suse.de ------------------------------------------------------------------------------- SUSE LINUX GmbH GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Hi Stefan, did you think whether it would be possible to extend this to testing AutoYaST upgrade as well? Is there anything that prevents extending it - except that you need to have an image to start with? Jiri On 03/04/2015 10:41 AM, Stefan Schubert wrote:
Hi, I have written a little test framework for running AutoYaST integration tests by using veewee, vagrant and pennyworth. I have not written something new but have only taken already existing tools and workflows.
Features
* Building KVM images by using AutoYaST profiles. * Checking these KVM images with rspec tests. * Generating own installation ISOs with local built RPMs or the newest one from OBS.
From my point of view it helps me to make changes in AutoYaST and running complete integration tests before submitting the package to OBS/IBS.
If you are interested please have a look to: https://github.com/schubi2/autoyast_test
Greetings Stefan
-- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.com Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.com -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Hi Jiri, good point ! I think this should be doable with not too much effort. Either in veewee or in pennyworth while the testing work flow. I am tending more to pennyworth because it is more fexible....but we will see Greetings Stefan Am 04.03.2015 um 11:09 schrieb Jiri Srain:
Hi Stefan,
did you think whether it would be possible to extend this to testing AutoYaST upgrade as well?
Is there anything that prevents extending it - except that you need to have an image to start with?
Jiri
On 03/04/2015 10:41 AM, Stefan Schubert wrote:
Hi, I have written a little test framework for running AutoYaST integration tests by using veewee, vagrant and pennyworth. I have not written something new but have only taken already existing tools and workflows.
Features
* Building KVM images by using AutoYaST profiles. * Checking these KVM images with rspec tests. * Generating own installation ISOs with local built RPMs or the newest one from OBS.
From my point of view it helps me to make changes in AutoYaST and running complete integration tests before submitting the package to OBS/IBS.
If you are interested please have a look to: https://github.com/schubi2/autoyast_test
Greetings Stefan
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 4.3.2015 v 10:41 Stefan Schubert napsal(a):
Hi, I have written a little test framework for running AutoYaST integration tests by using veewee, vagrant and pennyworth. I have not written something new but have only taken already existing tools and workflows.
Features
* Building KVM images by using AutoYaST profiles. * Checking these KVM images with rspec tests. * Generating own installation ISOs with local built RPMs or the newest one from OBS.
Hi, looks really interesting! I haven't checked the details, but is it possible to run it automatically (without user interaction)? If yes then we should run it automatically in Jenkins... -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Am 04.03.2015 um 11:44 schrieb Ladislav Slezak:
Dne 4.3.2015 v 10:41 Stefan Schubert napsal(a):
Hi, I have written a little test framework for running AutoYaST integration tests by using veewee, vagrant and pennyworth. I have not written something new but have only taken already existing tools and workflows.
Features
* Building KVM images by using AutoYaST profiles. * Checking these KVM images with rspec tests. * Generating own installation ISOs with local built RPMs or the newest one from OBS. Hi,
looks really interesting! I haven't checked the details, but is it possible to run it automatically (without user interaction)? Yes. Currently it stops if an error happens. It works automatically if no error happens.
If yes then we should run it automatically in Jenkins... That's my intention:-) . It should work on both, local on your machine and on Jenkins too.
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 4.3.2015 v 13:03 Stefan Schubert napsal(a):
If yes then we should run it automatically in Jenkins... That's my intention:-) . It should work on both, local on your machine and on Jenkins too.
Great, thanks! -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Wed, 04 Mar 2015 13:03:53 +0100
Stefan Schubert
Am 04.03.2015 um 11:44 schrieb Ladislav Slezak:
Dne 4.3.2015 v 10:41 Stefan Schubert napsal(a):
Hi, I have written a little test framework for running AutoYaST integration tests by using veewee, vagrant and pennyworth. I have not written something new but have only taken already existing tools and workflows.
Features
* Building KVM images by using AutoYaST profiles. * Checking these KVM images with rspec tests. * Generating own installation ISOs with local built RPMs or the newest one from OBS. Hi,
looks really interesting! I haven't checked the details, but is it possible to run it automatically (without user interaction)? Yes. Currently it stops if an error happens. It works automatically if no error happens.
If yes then we should run it automatically in Jenkins... That's my intention:-) . It should work on both, local on your machine and on Jenkins too.
Question is if we then need real hardware worker instead of virtual one, as now we already virtualize jenkins workers, so running KVM can be quite tricky in jenkins. But it is really interesting idea and real worker can be solvable. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Am 04.03.2015 18:21, schrieb Josef Reidinger:
On Wed, 04 Mar 2015 13:03:53 +0100 Stefan Schubert
wrote: Am 04.03.2015 um 11:44 schrieb Ladislav Slezak:
Dne 4.3.2015 v 10:41 Stefan Schubert napsal(a):
Hi, I have written a little test framework for running AutoYaST integration tests by using veewee, vagrant and pennyworth. I have not written something new but have only taken already existing tools and workflows.
Features
* Building KVM images by using AutoYaST profiles. * Checking these KVM images with rspec tests. * Generating own installation ISOs with local built RPMs or the newest one from OBS. Hi,
looks really interesting! I haven't checked the details, but is it possible to run it automatically (without user interaction)? Yes. Currently it stops if an error happens. It works automatically if no error happens. If yes then we should run it automatically in Jenkins... That's my intention:-) . It should work on both, local on your machine and on Jenkins too.
Question is if we then need real hardware worker instead of virtual one, as now we already virtualize jenkins workers, so running KVM can be quite tricky in jenkins.
But it is really interesting idea and real worker can be solvable.
Josef A good point. That's why machinery uses pennyworth. As far I have understood you can run pennyworth on distributed systems. Machinery runs e.g. different test on different architectures. So it is a mixture of jenkins and real hardware. But I have to investigate more time for.....or asking the machinery team for :-)
Greetings Stefan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (5)
-
Jiri Srain
-
Josef Reidinger
-
Ladislav Slezak
-
Stefan Schubert
-
Stefan Schubert