On 1/18/06, Tim Ellison <[EMAIL PROTECTED]> wrote:
...
> In my world, 'implementation tests' and 'API tests' can both be Unit
> tests (i.e. that's the style of test, not what they are testing). I
> disagree with Stepan that all tests should be defined in the same
> package as the implementation a
Geir Magnusson Jr wrote:
> Tim Ellison wrote:
>> Stepan Mishura wrote:
>>> A test framework is quite essential part and we should define it on
>>> early
>>> stage.
>>>
>>> I think first we should agree on which test we are going to provide
>
I don't think anyone is suggesting that we move the implementation
classes onto the application classpath -- as you say, there would be a
riot of renaming and native fix-ups required that would make this a
non-trivial task.
Regards,
Tim
Rodrigo Kumpera wrote:
> I think allowing tests to be fully
Tim Ellison wrote:
Stepan Mishura wrote:
A test framework is quite essential part and we should define it on early
stage.
I think first we should agree on which test we are going to provide and form
requirements to them. There are no doubts that we will provide unit tests
for classlib. So
Stepan Mishura wrote:
> A test framework is quite essential part and we should define it on early
> stage.
>
> I think first we should agree on which test we are going to provide and form
> requirements to them. There are no doubts that we will provide unit tests
> for classlib.
A test framework is quite essential part and we should define it on early
stage.
I think first we should agree on which test we are going to provide and form
requirements to them. There are no doubts that we will provide unit tests
for classlib. So unit tests are provided by code authors in JUnit
I think allowing tests to be fully executable in Java (i.e. a
certified jvm) would be really tricky. Some black-magic to rename all
classes would be required, and testing some core functionality would
be really hard - think synchronization and threading.
But for most classes this is perfectly doab
One thing that's popped up on the "Test suite layout" thread is the
thought that we need to b0rk the canonical package and naming
conventions for unit tests in order to be able to run things on the boot
classpath of the VM. I think this issue is important enough and
fundamental enough to warra
