Release Engineering

That's something I'd like to hand over to the upcoming QA role primarily, so let's revisit this when they are onboard

With Xisco on board now, is there anything major time consuming on your plate left? Otherwise, I'd like to close/re-assign this ticket and have Xisco coordinate with Björn on it

Florian Effenberger wrote:

With Xisco on board now, is there anything major time consuming on your plate left? Otherwise, I'd like to close/re-assign this ticket and have Xisco coordinate with Björn on it

I would like to continue to participate there. Currently, it's useless to go on with MozTrap as the version we used is not maintained for 4 years and need to be updated. There is an open source tool named Tarantula and I would like to give it a try http://www.testiatarantula.com/n but I didn't get an answer from Bjoern about it.
The reason I would like to go on with manual testing is because it's about community building together with QA.

I would like to continue to participate there. Currently, it's useless
to go on with MozTrap as the version we used is not maintained for 4
years and need to be updated. There is an open source tool named
Tarantula and I would like to give it a try
http://www.testiatarantula.com/n but I didn't get an answer from Bjoern
about it.
The reason I would like to go on with manual testing is because it's
about community building together with QA.

Can you sync with Marina and Osvaldo (both are board oversight for QA)
to get their feedback on whether manual testing makes sense? I can't
judge - I think it does make sense, but I'd like to have some qualified
feedback on that. :-)

If the outcome is positive, we can look into factoring some time to get
Tarantula setup.

Current plan is to use TestLink, feedback TBD

Current status is that Sophie and Xisco are working on setting things up, plan is to have it ready end-April for the next BHS
Sophie, correct me if that is wrong :-)

Florian Effenberger wrote:

Current status is that Sophie and Xisco are working on setting things up, plan is to have it ready end-April for the next BHS
Sophie, correct me if that is wrong :-)

It's correct :)

What's the current TestLink status?

It is up and running. I've incorporated some feedback I get during the BHS, but as the alpha build was late, very few have run the tests. I've worked on the localization process (on FR only for the moment) and it's ready to be populated for the l10n teams who want to participate. I've also documented it on the wiki. I would like to discuss with Xisco on how to proceed further steps during the next QA meeting.

Any update on TestLink? Are things up and running? How is the acceptance?
Anything missing or blocking production use?

I need to discuss it with Xisco during LibOCon. For the moment it is stalled, we need to define a process where automated tests are not duplicated in testlink and where manual tests are useful both for developers and l10n teams. Also the list of tests have to be updated on a regular basis.

Sophie Gautier wrote:

I need to discuss it with Xisco during LibOCon. For the moment it is stalled, we need to define a process where automated tests are not duplicated in testlink and where manual tests are useful both for developers and l10n teams. Also the list of tests have to be updated on a regular basis.

Is that a discussion we can kick off already earlier on, e.g. during one of the next QA calls and all-in team meetings?

Discussing with Xisco and Sophie pending to see how to move this forward

Was there any outcome at LibOCon on how to proceed?

Update on this:
Xisco has created a wiki page:
https://wiki.documentfoundation.org/ListUiTests
running a script he wrote:
https://gerrit.libreoffice.org/#/c/45496/
to be run from bin dir using ./list-uitest.py

by the end of the year, I'll update TestLink accordingly, remove duplicates with unittests, add tests for new functionnalities.

Update: Raal is writing automatic UI tests so we discussed (with him, Xisco and me) to not overlap between his work and TestLink.
I'll work on "everything related to mouse gestures (ie. insert a shape where drag&drop is needed). Besides, the uitests use the uno commands directly, meaning, it doesn't care if the menu/sidebar/toolbar entry exists or not, so the menus, sidebar and toolbars are not covered by the uitests. Manual tests are also good to tests the translations are ok and make sense and everything looks good in the UI. The uitests don't check the position of the objects in the dialogs."

To try to engage more people in both processes, during the last QA meeting, we have decided to add NeeUITest keyword to the bugs who need either manual or automatic UI tests. I tagged a first list, based on Raal input:
https://bugs.documentfoundation.org/buglist.cgi?keywords=needUITest&list_id=775877

Next step is to update wiki pages to get rid of MozTrap processes - remaining is mostly how to write UI tests on TestLink.

Can you give me a status update on where we stand with MozTrap, if anything is needed, any blockers or questions? ;-)

I set a test session for the last BHS but it has not been used, it seems nobody was interesting by running manual tests. I'll set another one for the next BHS on the beta.

If there's no progress, can you talk to Xisco and those in the board
with oversight on QA whether to keep this task?