On Thursday, April 02, 2015 10:44:31 AM Raymond Wooninck wrote:
On Thursday, April 02, 2015 10:27:57 AM Alberto Planas
> Anyone can write test for openQA. We only need to submit the
Looking at which KDE applications are being tested,
then the main
would be to get new screenshots as that the main menu
would change. The logic behind it are calling the
programs that will
really change name (e.g. kate, amarok, kontact). Only
would have to call systemsettings5 :)
This is good news. This means that when the change is staged by Max,
the amount of change in code will be minimal.
My recommendation here is something like this:
* Ask coolo or lnussel for an user in http://openqa.opensuse.org
can restart jobs and can needle (select region of interest in openQA)
* Before the change in TW, check the current tests running today in
* Write a couple of test for KDE4 that can be relevant for KDE5 too, but
that are missing today.
* Submit the tests to the opeQA tests repo:
In this moment the staging projects and post-integration test are going
to start failing, because you provide the tests but not the asserts
* Use your openQA account to create the needles and restart the KDE
failing jobs until we are green again!
In this moment you know most of the things about openQA, so you can
start planning more test relevant only to the goals that the team have
for KDE5. You can submit them after KDE5 is staged.
As that KDE is the default desktop a lot of the
screenshots needs to
changed. Is this something that we need to create
ourselves, or is
process here, that we adjust the logic, update github,
default and then just run the tests ? The tests that
fail can then be
adjusted/fixed inside the openQA interface based on the screenshots
openQA is creating ?
Thanks to the staging projects both a good approach: KDE5 is going to
broke the needles, and this is not important. The important things are
(IMHO) the missing tests that are for KDE5 but we need yet to
implement, in order to be sure that KDE is working as expected.
So I think that a good strategy is start playing with openQA with KDE4,
provide one or two more tests to really understand how it works and
how to fix the test (hard to do) and provide the needles (easy to do).
Apologies for these questions, but I never worked with
I really believe that this is a-ma-zing! I am sure that once the KDE team
will play with openQA to see how important is to TW and openSUSE,
more contributors will provide dozen of new test for systemd, the
kernel, LO and more important components for the system.
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: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org