Re: New Volounteer for Testing

Hi Markus,

happy to hear from you!
UI testing topic sounds for me very interessting. It will be great to know
how it works and how can I add more test.
The other issue is that I did not receive the response from Xisco in my
email. I saw it the mailing list archive after I read your message.

For Testlink I think an only Admin can  create an account for me.

[1] https://bugs.documentfoundation.org/  : Account is created and works

[2] https://wiki.documentfoundation.org/QA/GetInvolved : already read.

[3] https://wiki.documentfoundation.org/TestLink: account needed

[4] https://wiki.documentfoundation.org/Development/UITests: read

[5] http://dev-builds.libreoffice.org/daily/master/

[6] https://wiki.documentfoundation.org/QA: still going through the
topic under this page

[7]. https://wiki.documentfoundation.org/QA/IRC

[8]. https://t.me/LibreOffice_QA

[9]. https://wiki.documentfoundation.org/QA/Mailing_List

Regards

Driss


2018-01-22 23:41 GMT+01:00 Markus Mohrhard <markus.mohrhard@googlemail.com>:

> Hello Driss,
>
> On Mon, Jan 22, 2018 at 10:06 AM, Driss Ben Zoubeir <
> driss.zoubeir@gmail.com> wrote:
>
> > Hi libre office community,
> >
> > my name is Driss from Munich. I started before 3 years as Volounteer in
> > Open Office  community and successfully solved some bugs. Now I want to
> > contribute to libre office, but in Testing. I know this is the developer
> > mailing list, but according to the website of libre Office I have to
> > contact the devoloper list, if I want to help in programming automated
> > tests.
> >
> > I have about 3 to 6 hours or even more per Week to Help with Testing. I
> > already have some basic knowledge on Testing: Google Test, Unity, Google
> > Mock, CMock, Tessy, jenkins...
> >
> > I would appreciate if you can Help me to start contributing on Testing.
>
> I see that you already have some experience with testing frameworks so I
> wanted to add a few more options to Xisco's answer. LibreOffice has a large
> automated testing framework based on cppunit that is run during the build.
> Most of these tests are unit and integration tests but many of them require
> quite some understanding of how the corresponding code works to be able to
> add a test. However if you have some area that you are especially
> interested we might be able to find ways that you can contribute to these
> tests without deep knowledge of the corresponding code.
>
> Additionally, we have as Xisco managed a new UI testing framework that is
> written in python and is built on top of the python unittest module. One of
> our volunteers has been quite active adding writer UI tests in the last few
> weeks (https://gerrit.libreoffice.org/#/q/owner:zcrhonek%
> 2540gmail.com+status:open). If you are interested we can give you some
> more background how these tests work, how to extend the test framework and
> how to add additional useful tests. As an example many of the test case in
> TestLink could be converted from manual tests to automated UI tests or
> integration tests.
>
> If you are still interested in a more coding related testing effort but
> none of the two above look that interesting to you I still have one or two
> ideas for automated testing that have not been started or not yet been
> ready. These mostly are python based testing concepts for problems that can
> not be tested with the existing frameworks.
>
> Regards,
> Markus