[opensuse-factory] How does one tests packages with the new Factory model?
Hi. Now that Factory/Tumbleweed are not to test things, how do you tests packages? For example, LXDM fails in the first boot after installation. The package builds fine in its project, and if you install it to replace another DM it works too. But as said before, it doesn't work in a fresh install. So how do you test cases like this? Do you have to build an image with your modified packets and install it to see if all goes well? Greetings. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 23 November 2014 at 15:35, jcsl
Hi.
Now that Factory/Tumbleweed are not to test things, how do you tests packages? For example, LXDM fails in the first boot after installation. The package builds fine in its project, and if you install it to replace another DM it works too. But as said before, it doesn't work in a fresh install.
So how do you test cases like this? Do you have to build an image with your modified packets and install it to see if all goes well?
Greetings.
Why don't you just use the ISO provided by openQA when the tests fail? That's what the 'download ISO' link is there for, so people can reproduce the exact build that openQA used when it found issues. To expand my suggestion as a full 'how to test Factory' process, this would be my advice 1) Build Package in Devel Project 2) Test package from Devel Project 3) If Problems = NULL then Submit to Factory 4) Wait for Staging and Acceptance, then monitor openQA test results for openSUSE-Tumbleweed at https://openqa.opensuse.org/tests/ 5) If tests fail, click on the 'Download iso' link on the left hand side of the test results screen, use that ISO to reproduce the scenario on your own setup/VM's, fix bug, resubmit In the case of this LXDM issue, it only seems to appear during that last, Step 5, of testing, else it would have been caught earlier, such as during Staging Hope this helps Rich -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi. El Domingo, 23 de noviembre de 2014 18:36:49 Richard Brown escribió:
On 23 November 2014 at 15:35, jcsl
wrote: Hi.
Now that Factory/Tumbleweed are not to test things, how do you tests packages? For example, LXDM fails in the first boot after installation. The package builds fine in its project, and if you install it to replace another DM it works too. But as said before, it doesn't work in a fresh install.
So how do you test cases like this? Do you have to build an image with your modified packets and install it to see if all goes well?
Greetings.
Why don't you just use the ISO provided by openQA when the tests fail? That's what the 'download ISO' link is there for, so people can reproduce the exact build that openQA used when it found issues.
To expand my suggestion as a full 'how to test Factory' process, this would be my advice
1) Build Package in Devel Project 2) Test package from Devel Project 3) If Problems = NULL then Submit to Factory 4) Wait for Staging and Acceptance, then monitor openQA test results for openSUSE-Tumbleweed at https://openqa.opensuse.org/tests/ 5) If tests fail, click on the 'Download iso' link on the left hand side of the test results screen, use that ISO to reproduce the scenario on your own setup/VM's, fix bug, resubmit
In the case of this LXDM issue, it only seems to appear during that last, Step 5, of testing, else it would have been caught earlier, such as during Staging
Hope this helps
Rich
Thanks, sure that it helps. But there is one scenario where I think this approach would not be adequate. LXDM, again, had a previously working version. In case of a show stopper bug like LXDM's one, you can re-submit the old working version of the package and work with the new version until it's fixed, then submit it again. This way Factory doesn't gets stuck until the problem is fixed (that can take some time). But you need a way to achive this. I don't know if you can simply "uncompress" the ISO file, change the package, and create a new ISO with the directory content to test the changes... I've tried several times to build images with SUSE Studio but none have worked. Greetings. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
jcsl
-
Richard Brown