Done on my side for the report: * Converted the Groovy Scriptler script "attach selenium screenshot to the failing tests’s descriptions” to a Jenkins pipeline script. See https://github.com/xwiki/xwiki-jenkins-pipeline/blob/26be6df7796fa271d93212f... Thanks -Vincent
On 1 Jun 2017, at 09:29, Vincent Massol <[email protected]> wrote:
On 1 Jun 2017, at 09:24, Thomas Mortagne <[email protected]> wrote:
Hi devs,
The idea today is to do a Test Day with priority to fixing long standing flickering (integration mostly) tests.
You can find known flickering tests on http://jira.xwiki.org/issues/?filter=14240. The goal is to really fix them, not just add some random wait here and there ;)
If you are not confident with the area around those specific flickering tests here are some other ideas for today: * obviously add more tests and increase the code coverage * move tests from enterprise to platform. Needed for the platform flavor and removal of XE * update jacoco covering setup (we often forget to increase it when adding more tests) * move more tests from JMock to Mockito * work on new test setups and tools: ** improve docker containers for packaging XWiki (possibly several for multiple DBs and Servlet containers).
Done mostly. Status: done for mysql + postgresql on tomcat.
What’s left: https://jira.xwiki.org/issues/?jql=project%20%3D%20XDOCKER%20AND%20resolutio...
** work on spreading Jenkins platform job into one job per maven module so that build can be spread on various agents (groovy scripting)
Note= This is to be tied with the pipeline move below since it’s related.
** Research/Use Jenkins 2 Pipeline plugin with the new DSL and commit the jenkinsfile in SCM
This is already done. What’s left and what I’m currently working on: * Port the "attach screenshot on failure to job page” script to pipeline * Port the "false positive check" script to pipeline * Move xwiki-commons, rendering, platform to JenkinsFile once the previous 2 items are done
Thanks -Vincent
** Test platform to run contrib extension tests on various versions of XWiki automatically * Speedup existing tests (research xwiki startup time, remove unnecessary modules, etc)
When what you fix can be linked to a Jira issue (sure you can create a jira issue for adding new tests this time :)), tag it with "testday" (same idea as "bugfixingday" when doing BFD). If not then answer to this mail to explain what you did.
Good Test Day !