Hi, Am 14.08.2015 um 10:50 schrieb Lukas Ocilka:
I've seen the progress in our last sprint and most of our delaying was caused by "trying to implement" some openQA test. This means we are fixing half of bugs we could.
Not sure if those test really decrease the overall bug fixing rate that much since not everyone was trying to create openQA-tests. However I think that it a self-healing issue, since after a while working with openQA one gets used to it and gets used to it and therefore gets much faster. At least that is what I can see for myself over the last few sprints where I created openQA tests.
As I see it, there are two ways of step over this problem:
1. Minimize creating openQA tests to a.) features b.) important issues that are likely to break in the future [short to mid term]
2. Make creating openQA tests a piece of cake, maybe by introducing some Yast library, maybe by contributing to openQA to make it well understandable, well documented [mid to long term]
I found a kind of workflow for implementing tests now. Unfortunately current openQA does not really support that workflow until now. So contributing to openQA would definitively help in speed up working with it. I'll see what I can do, as soon time permits. Mit freundlichen Grüßen, Christopher Hofmann -- Attachmate Group Germany GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton HRB 202401 (AG München) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org