[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [stellation-res] The unit test TODO is fuzzy to me.
|
On Wed, Jul 31, 2002 at 10:09:18PM +0100, Ringo De Smet wrote:
> Hello Florin & others,
>
> As a developer, I'm a test-first kind of guy. This means that I judge
> the quality of a piece of software on the amount of unit tests and if
> they all pass. This means that I want to add unit tests, but I couldn't
> deduce from the unit test TODO list what to do. Can the TODO list be a
> bit more detailed, so I can take up some of the work on the list?
Sure:
TODO:
* Stabilize the ProjectData package
- I am still thinking hard about this - we need a more flexible
project data set of interfaces and some better implementations.
The current interface works only with trivial trees - no
branches. - Needs to be fixed for testing merges.
There is no implementation for evolving directories:
adding/removing files as they "age". - Needs to be fixed for
merges and stress testing the backend
* JavaDuck
- Java docs. I usually put a wee bit of javadoc inside the source
but they evolved so wildly that any documentation become
obsolete very quickly. Hopefully the code is broken into bits
small enough to understand without javadoc. As things get more
stable, I will fill in the blanks.
* More ProjectData implementations
- See above: basically we need:
Files that grow and shrink.
Directories that grow and shrink.
Wide directories.
Deep directories.
Very_long_file_names.
Many filenames that differ by a single character.
Large files that age by changing a few bytes here and there.
Large files that change very much.
* Test Developer's Guide
- See above about the docs.
* MergeTest
- Create the implementations to support testing of merges. For
starters we need a ForkedProjectData that can evolve on two
branches.
* Implement Command-based RevisionServices
- The current RepositoryServices is implemented (almost) by calling
Svc.main . A command based RepositoryServices will bypass all
argument parsing and use more direct calls into stellation core.
Maybe it will be a tad faster that way to run large amounts of
tests.
Feel free to add anything you need to the TODO. This expanded list will
be in my next drop.
florin
--
"If it's not broken, let's fix it till it is."
41A9 2BDE 8E11 F1C5 87A6 03EE 34B3 E075 3B90 DFE4
Attachment:
pgpTIbW_1J_na.pgp
Description: PGP signature