Skip to main content
This revision made May 25, 2013 16:00, by Martijn Verburg


Test Fests are hackdays organised around the world with a focus to improving the quality and coverage of tests in OpenJDK. In particular IBM, Oracle and Java User Groups are pushing these days.

Running a Test Fest

What works

  • Spend less time up front explaining OpenJDK procedure and getting people to write tests
  • Get people to build Your Own Environment ahead of time
  • Pick specific areas to focus on for writing tests, e.g. The Base64 class and JSR 310 (Date and Time).
    • Narrow down the scope for these events as much as possible and perhaps even pick 1-3 classes to focus on that you know aren't tested.
    • Grepping source code for "TODO: more tests"

What didn't work

 * Code Coverage tools are lacking and reports unpublished - TBA Pavel from RedHat is working on this
 * Still need manual work to marshall commits into openjdk (should be solved by betterrev)
 * Testing JSR-310 required quite a bit of explanation since the things that are least tested are Japanese and Islamic calendaring systems which have a lot of local domain knowledge.  We should probably avoid this kind of stuff in future.

Types of activities

Back to WhatToWorkOnForOpenJDK
Back to AdoptOpenJDK

Difference compared to previous revision
<span>__TOC__ Test Fests are hackdays organised around the world with a focus to improving the quality and coverage of tests in OpenJDK<span style="text-decoration:underline;color:green">. In particular IBM, Oracle and Java User Groups are pushing these days.</span> <span style="text-decoration:underline;color:green"> = Running a Test Fest = == What works == * Spend less time up front explaining OpenJDK procedure and getting people to write tests * Get people to build [[Your Own Environment]] ahead of time * Pick specific areas to focus on for writing tests, e.g. The Base64 class and JSR 310 (Date and Time). ** Narrow down the scope for these events as much as possible and perhaps even pick 1-3 classes to focus on that you know aren't tested. ** Grepping source code for "TODO: more tests" == What didn't work == * Code Coverage tools are lacking and reports unpublished - TBA Pavel from RedHat is working on this * Still need manual work to marshall commits into openjdk (should be solved by [https://bitbucket.org/adoptopenjdk/betterrev betterrev]) * Testing JSR-310 required quite a bit of explanation since the things that are least tested are Japanese and Islamic calendaring systems which have a lot of local domain knowledge. We should probably avoid this kind of stuff in future. = Types of activities = * Writing new TestNG Tests</span> * [[Replace Shell Script Tests]] - lead by TBA Back to [[WhatToWorkOnForOpenJDK]]<br/> Back to [[AdoptOpenJDK]]<span>
 
 
Close
loading
Please Confirm
Close