As discussed. One green tab per test method (so at least one per score rule).

1) First fase requirements:

• Every single score rule must be unit tested! It's called the Bernard rule. (you can mention that in the blog article ).
• It should use the ScoreVerifier underneath.
• Reuse the Xlsx solution FileIO partially. (Don't make it more lenient for normal dataset reading, but do reuse common code).
  • One way might be to add a boolean parameter "unitTestRead=true" that if true makes it more lenient and looks for a the blue tab with a specific name (which is also a parameter I guess)

Attached is a napkin prototype of such an xls file. (Although it should not contain any yellow tabs probably)

2) Second fase: write a blog article about it.

• See result here https://www.optaplanner.org/blog/
• See sources here, send PR for that https://github.com/kiegroup/optaplanner-website/tree/master/blog
• First take a few hours to read a good documentation style guide https://developers.google.com/style/
  • Especially about active voice, etc
  • A blog post isn't really documentation, so not all rules apply
  • Especially in a blog, don't write monotonous, see https://twitter.com/buffer/status/891735670460493824
  • Images (screenshots, diagrams in Inkscape) are better then many paragraphs