Comment 1 Ilja Preuss 2006-01-19 10:03:06 EST

Ditto here!

Comment 2 Martin Aeschlimann 2006-01-20 06:17:02 EST

What we could do is to use the current selection if it extends TestCase. Is that good enough?

The problem of initializing a field is always that it is also nasty for the user when its wrong.

Comment 3 Ilja Preuss 2006-01-20 06:30:28 EST

(In reply to comment #2)
> What we could do is to use the current selection if it extends TestCase. Is
> that good enough?
> The problem of initializing a field is always that it is also nasty for the
> user when its wrong.

At work, we have our own root TestCase class that adds a number of commonly used assert methods. We want to use that one in 99% of all cases.

So, no, for us using the current selection wouldn't work - initializing the field with a value defined once is exactly what we want.

What would also work is if the field remembered its last value, perhaps even with a history.

(This might become less relevant with JUnit 4, I guess...)