As the amount of code is beginning to reach a critical
mass, every class should have an automated unit test.
This is needed for regression test purposes and to
ensure developers don't check in code that breaks
existing functionality.
As far as I can see there are two types of tests.
1. It should be easy to write junit tests for model and
data access classes. So I expect these to be written.
2. Automated testing of the front end is a bit more
involved. We should look into how this can be achieved
e.g. cactus or httpunit.
To separate the code, perhaps we should create a new
project and package structure e.g.
unittest.j2eeslashcode.UserTest etc.
Nigel Wetters Gourlay
None
None
Public
|
Date: 2002-06-04 19:55 Logged In: YES |
|
Date: 2002-05-30 22:44 Logged In: YES |
|
Date: 2002-05-29 16:01 Logged In: YES |
|
Date: 2002-05-23 23:41 Logged In: YES |
|
Date: 2002-05-22 08:33 Logged In: YES |
| Field | Old Value | Date | By |
|---|---|---|---|
| assigned_to | cwatana | 2002-06-04 19:55 | cwatana |
| assigned_to | nwetters | 2002-05-29 16:01 | nwetters |
| assigned_to | cwatana | 2002-05-23 23:41 | cwatana |
| assigned_to | nwetters | 2002-05-22 08:33 | nwetters |