From: James Macgill <j.macgill@ge...> - 2002-01-29 11:24:18
I have set up the task list for the topics raised in this mornings IRC session.
You can see the list at:
I know who I should be assigning each task to, but lets start as we intend
to go on, could you assign the tasks to yourselves.
Make an estimate of the number of idea programming hours it will take you
(assuming no interruptions or other commitments) and also set an estimated
If, whilst you are working on a task, you think of a new task that needs
doing then please create it and if necessary, make your task dependent on it.
Center for Computational Geography
Spell Checker (c) Creative Spelling inc (aka my dyslexic brain)
http://www.geotools.org the open source java mapping toolkit.
From: Artur Hefczyc <wislaj23@wp...> - 2002-02-08 15:26:37
I recently have some troubles with access
to internet so I couldn't activelly
take part in IRC discusion and geotools-devel
discusions about geotools2 plans.
However I worked hard and prepared new version of
unitestsgen which I think can help to improve
one part of developing process.
At the moment unittestsgen can be used as ANT task.
With two additional features: updating test classes code
according to changes are made in source files and puts
code to new test methods which generates JUnit error
It gives us one new advantage. We can very easy discover
all new code which is not covered by test code in unit tests.
And we can use it as one of condition for putting new code
in devel release code or stable code or somewhere else.
You can create build.xml to preform following actions:
1. Compile all source classes (with test classes)
2. Run unittestsgen on new compiled code
3. Compile test classes again
4. Run JUnit tests
If unit tests generator will find any changes and add new
test methods JUnit will always report unit tests errors.
So we can know that existing code is not ready yet for putting
in stable branch.
It seems to be useful and I use it at the moment in my development
and even in my existing company it is introduced into all
Of course I can't guarantee that it is the best way but
it is possible to put some modifications in both development
process and in this tool.
From: James Macgill <j.macgill@ge...> - 2002-02-11 17:41:49
>You can create build.xml to preform following actions:
>1. Compile all source classes (with test classes)
>2. Run unittestsgen on new compiled code
>3. Compile test classes again
>4. Run JUnit tests
I very much like the sound of this, can we look at how to start putting
this in place? I have added some code to the CVS repository and I was
planning to start adding test cases to it soon, so it would be good to have
your system in place first.