Eclipse and JUnit [was: Re: Font work (CLA needed)]

[Simon Pepping <sp...@leverkruid.nl>]

On Mon, Dec 19, 2005 at 08:52:59PM +0100, Jeremias Maerki wrote:
> 
> On 19.12.2005 20:06:26 Vincent Hennebert wrote:
> > Moreover my patched Fop still doesn't pass the unitary tests. I'm trying to 
> > figure out what is going on but so far I've spent more time fighting against 
> > Eclipse to make the debugger work on the junit system than searching for errors. 
> > Not sure yet if I've won.
> 
> Hmm, so far I've had no problems debugging inside Eclipse's JUnit
> environment.

I try to avoid it by running fop directly with the XSL stylesheet
test/layoutengine/testcase2fo.xsl, or I even generate the FO using
this stylesheet.

Maybe unnecessary, but if you are not so experienced with eclipse, you
can have a hard time to make it do what you want. Avoiding JUnit in
the debugging process helps me.

Simon

-- 
Simon Pepping
home page: http://www.leverkruid.nl

Re: Eclipse and JUnit

[Jeremias Maerki <de...@jeremias-maerki.ch>]

On 21.12.2005 14:50:58 Simon Pepping wrote:
> On Wed, Dec 21, 2005 at 11:03:59AM +0100, Jeremias Maerki wrote:
> > Yes, digging up the right system properties is a nuisance, but you only
> > have to do it once. Have a look at the attached screen shots that show
> > how I set up the launch config for running the FOP test suite. You can
> > see that I simply add an "x" somewhere to effectively disable the
> > setting for a system property. Like this I'm can change the parameters to
> > the test suite very quickly. Maybe that helps make things easier.
> 
> Thanks. The "x" is a nice trick.
> 
> It would be good to have a document describing the system properties
> of the test suites. If you do not do it, I will write one.

I've started documentation about the layout engine test suite here:
http://wiki.apache.org/xmlgraphics-fop/HowToCreateLayoutEngineTests

I'm going to add some notes about the various system properties in a few
minutes.

> I see you have a project 'FOP Temp', which probably is a copy of
> project FOP. I have a problem making a copy of a project, when I make
> a copy of the working directory for a specific task. Esp. one has to
> duplicate the lauch configurations. I solve it by reusing the same
> symlink on Unix. Is there an easier way to work with a changing set of
> copies of the working directory?

Well, being on Windows I don't have symlinks. I simply check out from
the same SVN URL again and switch the project dependency in my project
with my custom FOP test code from one FOP checkout to the other. Not
ideal but not a big deal for me.


Jeremias Maerki

Re: Eclipse and JUnit

[Simon Pepping <sp...@leverkruid.nl>]

On Wed, Dec 21, 2005 at 11:03:59AM +0100, Jeremias Maerki wrote:
> Yes, digging up the right system properties is a nuisance, but you only
> have to do it once. Have a look at the attached screen shots that show
> how I set up the launch config for running the FOP test suite. You can
> see that I simply add an "x" somewhere to effectively disable the
> setting for a system property. Like this I'm can change the parameters to
> the test suite very quickly. Maybe that helps make things easier.

Thanks. The "x" is a nice trick.

It would be good to have a document describing the system properties
of the test suites. If you do not do it, I will write one.

I see you have a project 'FOP Temp', which probably is a copy of
project FOP. I have a problem making a copy of a project, when I make
a copy of the working directory for a specific task. Esp. one has to
duplicate the lauch configurations. I solve it by reusing the same
symlink on Unix. Is there an easier way to work with a changing set of
copies of the working directory?

Simon

-- 
Simon Pepping
home page: http://www.leverkruid.nl

Re: Eclipse and JUnit

[Jeremias Maerki <de...@jeremias-maerki.ch>]

Yes, digging up the right system properties is a nuisance, but you only
have to do it once. Have a look at the attached screen shots that show
how I set up the launch config for running the FOP test suite. You can
see that I simply add an "x" somewhere to effectively disable the
setting for a system property. Like this I'm can change the parameters to
the test suite very quickly. Maybe that helps make things easier.

On 21.12.2005 10:46:33 Simon Pepping wrote:
> On Wed, Dec 21, 2005 at 09:48:52AM +0100, Jeremias Maerki wrote:
> > That's very unfortunate. Can you guys explain to me what exactly the
> > problems are? Maybe I can help. It is very helpful to simply run a
> > single test under JUnit control directly from Eclipse. I simply have to
> > specify the test case I want to run in the system properties and off I
> > go.
> 
> Running a single test is always a problem, with ant and with
> eclipse. The point is just that I do not do this often, and everytime
> I have to look through the test suite code to dig up the exact system
> property to set.
> 
> Eclipse is a bewildering huge beast when you start with it. I have
> just spent some time learning how to use it properly, and now I feel
> more comfortable with it. I suppose it is a matter of habit. At the
> moment I happen to write scripts more easily than eclipse launch
> configurations. So I tend to avoid complications and use the simplest
> solution.


Jeremias Maerki

Re: Eclipse and JUnit

[Simon Pepping <sp...@leverkruid.nl>]

On Wed, Dec 21, 2005 at 09:48:52AM +0100, Jeremias Maerki wrote:
> That's very unfortunate. Can you guys explain to me what exactly the
> problems are? Maybe I can help. It is very helpful to simply run a
> single test under JUnit control directly from Eclipse. I simply have to
> specify the test case I want to run in the system properties and off I
> go.

Running a single test is always a problem, with ant and with
eclipse. The point is just that I do not do this often, and everytime
I have to look through the test suite code to dig up the exact system
property to set.

Eclipse is a bewildering huge beast when you start with it. I have
just spent some time learning how to use it properly, and now I feel
more comfortable with it. I suppose it is a matter of habit. At the
moment I happen to write scripts more easily than eclipse launch
configurations. So I tend to avoid complications and use the simplest
solution.

Simon

-- 
Simon Pepping
home page: http://www.leverkruid.nl

Re: Eclipse and JUnit [was: Re: Font work (CLA needed)]

[Jeremias Maerki <de...@jeremias-maerki.ch>]

That's very unfortunate. Can you guys explain to me what exactly the
problems are? Maybe I can help. It is very helpful to simply run a
single test under JUnit control directly from Eclipse. I simply have to
specify the test case I want to run in the system properties and off I
go.

On 21.12.2005 09:34:07 Simon Pepping wrote:
> On Mon, Dec 19, 2005 at 08:52:59PM +0100, Jeremias Maerki wrote:
> > 
> > On 19.12.2005 20:06:26 Vincent Hennebert wrote:
> > > Moreover my patched Fop still doesn't pass the unitary tests. I'm trying to 
> > > figure out what is going on but so far I've spent more time fighting against 
> > > Eclipse to make the debugger work on the junit system than searching for errors. 
> > > Not sure yet if I've won.
> > 
> > Hmm, so far I've had no problems debugging inside Eclipse's JUnit
> > environment.
> 
> I try to avoid it by running fop directly with the XSL stylesheet
> test/layoutengine/testcase2fo.xsl, or I even generate the FO using
> this stylesheet.
> 
> Maybe unnecessary, but if you are not so experienced with eclipse, you
> can have a hard time to make it do what you want. Avoiding JUnit in
> the debugging process helps me.
> 
> Simon
> 
> -- 
> Simon Pepping
> home page: http://www.leverkruid.nl



Jeremias Maerki