diff options
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20130329/790c34e6/attachment-0001.html')
| -rw-r--r-- | zarb-ml/mageia-dev/attachments/20130329/790c34e6/attachment-0001.html | 74 |
1 files changed, 74 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20130329/790c34e6/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20130329/790c34e6/attachment-0001.html new file mode 100644 index 000000000..33145262b --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20130329/790c34e6/attachment-0001.html @@ -0,0 +1,74 @@ +<p dir="ltr"><br> +On 28 Mar 2013 00:57, "Glen Ogilvie" <<a href="mailto:nelg@linuxsolutions.co.nz">nelg@linuxsolutions.co.nz</a>> wrote:<br> +><br> +> Hi,<br> +><br> +> Has anyone done, or thought about, setting up some automated testing<br> +><br> +> of the Mageia installer?<br> +><br> +> I am thinking something based on:<br> +><br> +> <a href="https://wiki.mageia.org/en/Auto_inst">https://wiki.mageia.org/en/Auto_inst</a>, testing inside a VM, with<br> +><br> +> a range of different installer configurations, like:<br> +><br> +> * different languages<br> +><br> +> * Free / non-free<br> +><br> +> * package selections, minimal, full, custom<br> +><br> +> * partitioning optons<br> +><br> +> * LVM options<br> +><br> +> * encryption options<br> +><br> +> * filesystem types<br> +><br> +> * software raid options<br> +><br> +> * known error cases (too small / filesystem), /boot on something not supported<br> +><br> +> * grub and grub2<br> +><br> +> * different CPUs, RAM, architectures.<br> +><br> +> I am thinking that if we had an auto-inst, with maybe 50 or so<br> +><br> +> different test cases, all of which would then be verified by an ssh<br> +><br> +> script connecting to the VM, or something like that.<br> +><br> +> I've found 3 bugs recently, all of which would have been able to be<br> +><br> +> detected by something like what I am suggesting.<br> +><br> +> Suggestions so far are:<br> +><br> +> nicolas vigier:<br> +><br> +> * For automatic testing it would be possible to use OS-autoinst :<br> +><br> +> <a href="http://www.os-autoinst.org/">http://www.os-autoinst.org/</a><br> +><br> +> * What we need is someone to add support for Mageia installer :<br> +><br> +> <a href="https://github.com/bmwiedemann/os-autoinst/tree/master/distri">https://github.com/bmwiedemann/os-autoinst/tree/master/distri</a><br> +><br> +> Pierre-Malo Deniélou:<br> +><br> +> "Great idea. Can you prototype it? We should use something like that for <br> +><br> +> mageia 4."<br> +><br> +> Anne Nicolas:<br> +><br> +> "I remember some people starting something about it Furthermore it could<br> +><br> +> be interested to have some virtualization for basic tests once rebooted"</p> +<p dir="ltr">We had been talking about it at Mandriva times but I don't remember if something was done.</p> +<p dir="ltr">Something like testing the install goes to the end + system starts with for example console on serial port in kvm to parse it for errors and check the dm comes up + maybe run run some automated test scripts.<br> + +</p> |