Nice start! On Fri, Jan 27, 2017 at 10:40 AM, Thomas Mortagne <[email protected] > wrote:
> Here is the result of this first experiment. > > http://www.xwiki.org/xwiki/bin/view/Blog/Test+Day+1. > > On Thu, Jan 26, 2017 at 9:32 AM, Thomas Mortagne > <[email protected]> wrote: > > Hi devs, > > > > Since nobody really answered the proposal until very late last week here > it is: > > > > 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 really not confident with the area around those specific > > flickering tests here are some other ideas for this kind of Day: > > * 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). > > ** work on spreading Jenkins platform job into one job per maven > > module so that build can be spread on various agents (groovy > > scripting) > > ** Research/Use Jenkins 2 Pipeline plugin with the new DSL and commit > > the jenkinsfile in SCM > > ** 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 an issue, 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 ! > > -- > > Thomas Mortagne > > > > -- > Thomas Mortagne >
