Recent changes to feature-requests

better names for test of methods with ar

Kaspar Lund — Wed, 07 Aug 2002 11:13:56 -0000

It is not possible to relate the name of a generated
methods for a methods with arguments.

Eks:
The original methods is named:
ComponentAdapter getComponent( String className )

The generated testmethod is name:
public void testGetComponent1195259493()

What about generating something like
public void testGetComponent_Args_className()

Support exclude tag in taskant.UnitTests

Ed MacDonald — Wed, 13 Feb 2002 03:52:25 -0000

Provide a way to tell UnitTestGen to skip certain
methods, classes, or packages during test generation.

Generate one testMethod for set/get pair

Ed MacDonald — Tue, 12 Feb 2002 02:58:26 -0000

Detect set/get pairs as found in beans and generate a
single test method.

Currently two test methods will be generated that do
the same thing.

Define new methods content

Artur Hefczyc — Mon, 07 Jan 2002 09:00:01 -0000

It is recommended to add feature which allow
define content of new created methods in
test classes. The possiblities are:
1. Empty content - the worst, but may be usefull in
some cases.
2. Content in created methods is fullfiled by comments
with usefull info.
3. Instead of comments or additionally to comments
there is possiblity to create unit test engine warning
which tells that this is empty test method and
real test code should be added

More default values of classes for tests

Artur Hefczyc — Sun, 30 Dec 2001 17:38:44 -0000

It seems that it could be useful to create more
default test values for test code for different
classes.
For example there are many commonly used classes
in packages:
java.io.*
java.net.*
java.util.*
and so on...

Hints for methods throwing exceptions

Artur Hefczyc — Sun, 30 Dec 2001 17:36:43 -0000

More hints for methods throwing exceptions are
necessary. Especially methods which throw
java.lang.Exception should be highlighted.

JUnit messages instead of just comments

Artur Hefczyc — Sun, 30 Dec 2001 17:34:42 -0000

It could be very useful if code generator could
create some piece of code generating JUnit messages
instead of just comments in Test classes for found
code hints.

If code analyser find strange or danger constructions
or simple find some useful info about classes, methods
and so on it can put comments inline in Test classes
code or maybe it should put some code which would
generate JUnit warning messages.

These messages could be found in JUnit reports.

Hints for public methods

Artur Hefczyc — Sun, 30 Dec 2001 17:27:28 -0000

There should be more hints for public methods
which could explain what for strange parameter
values should be prepared.

A way for creating default test values

Artur Hefczyc — Sun, 30 Dec 2001 17:20:14 -0000

It is recommended to create interface for
easy extending default test values for
different classes used in other projects.

This interface must be very easy to use
such as text file which contains:
class_name: list of default test values.

And maybe it could be posible to create simple
GUI for managing such files.

Config file for tests code generators

Artur Hefczyc — Sun, 30 Dec 2001 17:14:59 -0000

It is recommended to create posibility of
use config file for setting job parameters
instead of long list of command line parameters.