Anne,<br><br>On Sun, Apr 8, 2012 at 9:03 AM, Anne-Marie Mahfouf <br>>Yes this is maybe the best free tool to do the job. <br>>DO you or
anybody have used it already?<br>
><br>
>Thanks for your input,<br><br>Unfortunately I have no experience on this tool, but when I check all the next emails I'm glad there is a lot of feedback.<br><br>Percy<br><br><br><br><br><br><div class="gmail_quote">
On Sun, Apr 8, 2012 at 9:03 AM, Anne-Marie Mahfouf <span dir="ltr"><<a href="mailto:annemarie.mahfouf@free.fr">annemarie.mahfouf@free.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<div text="#000000" bgcolor="#ffffff"><div class="im">
On 04/08/2012 07:11 AM, Percy Camilo Triveño Aucahuasi wrote:
<blockquote type="cite">Hi Anne, hi all<br>
<br>
On Fri, Apr 6, 2012 at 12:03 PM, Anne-Marie Mahfouf <br>
>This is addressed for 4.9 as "putting in place a few <br>
>selected areas of functional testing" and hopefully <br>
>we will assess some automated UI testing tools <br>
>and start using them in the following releases. <br>
>I hope we can gather enough beta testers and <br>
>make this working.<br>
<br>
Indeed, Nice idea, I think this is the right focus to (auto)test
the functionality/features of the app. I've searched some info
about this topic and found this:<br>
<br>
<a href="http://ldtp.freedesktop.org/wiki/Home" target="_blank">http://ldtp.freedesktop.org/wiki/Home</a><br>
<br>
It has full support for KDE/Qt (>4.x) apps and the scripts (for
autotesting) can be written with Python.<br>
<br>
My 0.5 cents :)<br>
<br>
Cheers,<br>
Percy<br>
</blockquote></div>
Yes this is maybe the best free tool to do the job. DO you or
anybody have used it already?<br>
<br>
Thanks for your input,<br>
<br>
Anne-Marie<div><div class="h5"><br>
<blockquote type="cite"><br>
<div class="gmail_quote">On Fri, Apr 6, 2012 at 12:03 PM,
Anne-Marie Mahfouf <span dir="ltr"><<a href="mailto:annemarie.mahfouf@free.fr" target="_blank">annemarie.mahfouf@free.fr</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>On 04/06/2012 02:23 PM, Aleix Pol wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
On Thu, Apr 5, 2012 at 1:42 PM, Anne-Marie Mahfouf<br>
<<a href="mailto:annemarie.mahfouf@free.fr" target="_blank">annemarie.mahfouf@free.fr</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi,<br>
<br>
We would like to setup a Quality Testing Team within
KDE in order to better<br>
test our next KDE SC and make the beta process more
efficient.<br>
Attached is the first draft of the ideas I
brainstormed. Source .odt of this<br>
document is available at<br>
<a href="http://quickgit.kde.org/index.php?p=scratch%2Fannma%2Fquality-testing-doc.git" target="_blank">http://quickgit.kde.org/index.php?p=scratch%2Fannma%2Fquality-testing-doc.git</a><br>
<br>
(We can make it a public Google doc if it is more
convenient or an<br>
etherpad).<br>
<br>
The document roughly describes 2 areas of action:<br>
- reinforcement (labelled "Reinforce") of existing
structures (mainly<br>
targetted to developers and mainly relevant before the
beta stage of the<br>
release). This could<br>
<br>
be used as guidelines for new developers. Of course it
won't be newbies<br>
which will develop Unit Tests or check the code
quality. But some guidelines<br>
can<br>
be useful for libs outside Frameworks.<br>
An area of relevant reinforcement that can be
currently done is the Review<br>
process for new integration.<br>
- new infra-structures: this is labelled "New" in the
doc: this is what I<br>
would see to happen for the 4.9 release.<br>
<br>
<br>
A new mailing list has been set up in order to discuss
all this: please<br>
subscribe to it if you would like to be part of this<br>
<a href="https://mail.kde.org/mailman/listinfo/kde-testing" target="_blank">https://mail.kde.org/mailman/listinfo/kde-testing</a><br>
An IRC channel also was created on Freenode:<br>
#kde-quality<br>
<br>
Please join the mailing list and the IRC channel so we
can setup a plan to<br>
start putting all this in gear!<br>
<br>
Thanks in advance,<br>
<br>
Anne-Marie and Myriam<br>
</blockquote>
Hi!<br>
I think this project is a very interesting idea and
definitely<br>
something we need. Said that, I'd like to propose some
small changes<br>
on how this should be done.<br>
<br>
In the document there are some actions to be taken that
sound a bit<br>
too technical, for example it specifies reinforcing the
unit testing.<br>
This is something that we should have been doing already
and I don't<br>
see someone from the Quality Team going to a development
team and<br>
improving that.<br>
</blockquote>
</div>
</div>
Making unit tests is the developer task (and the document
mentions it) and we do have solit Unit Tests in kdelibs and
Frameworks and kdepimlibs. However there are other libs within
KDE where maybe unit tests are not as present as they should
(I did not research that though). Also, about unit tests, it's
not only writing them, it's also running them. This is not
done in a regular basis and needs to be automated in the
future and the fails need to be fixed.<br>
No newbie will ever touch to any Unit Tests of course. And any
action will be discussed with the gurus in this field (/me
does not point to David).<br>
<br>
We have many tools for developers which are not fully used:
latest great tool is Jenkins which I was aware of only
recently. My label "Reinforce" is to take full advantage of
those existing tools.<br>
<br>
(It would be cool if at Akademy there are some talks focusing
on using these tools.)
<div><br>
<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
What I'd like to see is this new team testing KDE and its
applications<br>
from a user perspective, specifying the different
perspectives the KDE<br>
end user will face (different OS, different form factors,
etc) and<br>
reporting problems (not necessarily bugs, as in crashes)
and proposing<br>
new solutions.<br>
</blockquote>
</div>
This is addressed for 4.9 as "putting in place a few selected
areas of functional testing" and hopefully we will assess some
automated UI testing tools and start using them in the
following releases. I hope we can gather enough beta testers
and make this working.
<div>
<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I'm really hopeful about such a team, I think it's a good
opportunity<br>
for KDE to be able to reach contributions for a less
common sector of<br>
our community and keep working together for a greater KDE
experience.<br>
<br>
Cheers!<br>
Aleix<br>
<br>
</blockquote>
</div>
Thanks for your input!<span><font color="#888888"><br>
<br>
Anne-Marie<br>
<br>
</font></span></blockquote>
</div>
<br>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br>