Hi Simon,

My apologies, I did float the idea about the layout engine tests and
kept to the suggestions that were given me. As such, creating tests is
exactly the same and the subset of tests run are still configurable
via System properties. The behaviour is the same, the only difference
made is in the implementation.

As for JUnit4 and Jacoco, these are primarily for developers and I'm
not sure what you wish to see documented? What would we document that
isn't repeating information readily available elsewhere?

If you have questions, I'd be more than happy to answer them, but
below I've included a couple informative links:

Here is a good introduction to Junit4:
http://www.ibm.com/developerworks/java/library/j-junit4/index.html

This is a fairly good analysis of Jacoco listing pros and cons, by the
people at Eclipse:
http://wiki.eclipse.org/JaCoCo/Proposal

There are plenty of other code-coverage tools, but I chose Jacoco for
predominantly a single feature: It can be used to analyse code
coverage of integration (end-to-end) tests. This would provide
valuable stats for assessing the testing framework.

http://www.eclemma.org/jacoco/trunk/doc/agent.html

Hope that helps

Mehdi

On 18 November 2011 18:42, Simon Pepping <spepp...@leverkruid.eu> wrote:
> Mehdi has recommended himself to the FOP team by taking new
> initiatives, such as Junit4 and Jacoco. But where is the
> documentation? See e.g. the wiki page HowToCreateLayoutEngineTests:
> Does that still apply? How do I know what jacoco is and how to run it?
> Should I just be in the know?
>
> Please, consider adding and updating documentation of new and renewed
> build and test tools.
>
> Simon
>

Reply via email to