| The Dev Test Framework will provide infrastructure required to create GlassFish Cluster and launch Dev Tests on it. It will be implemented on top of Hudson based setup. The intention is to use Hudson Cluster for GlassFish Cluster Dev Test Deployment. Feature Overview
| Feature ID |
Priority |
Description |
Eng Response |
Owner(s) |
Estimate (Man Days) |
Source of Requirement |
Status / Comments |
| DEVTEST-001-Plugin |
P1 |
Ability to create GlassFish cluster and run the tests |
Yes |
Harshad |
|
|
Hudson Plugin:
- 3 instances or more;
- number of instances is configurable.
- Hooks for ant scripts
- Note: This task is split into three phases.
- See milestone schedule 1.1, 1.2, 1.3 for details.
|
| DEVTEST-001-Ant |
P1 |
Ability to create GlassFish cluster and run the tests |
Yes |
Mathi |
|
|
Ant based:
- 3 instances or more;
- number of instances is configurable.
- Integrate with Hudson
- Note: This task is split into two phases.
- See milestone schedule 2.1, 2.2 for details.
|
| DEVTEST-002 |
P1 |
Portable and configurable for individual testing clusters |
Yes |
|
|
|
No hardwired machine names in the test framework |
| DEVTEST-003 |
P1 |
Hudson integration to automate the dev test execution on a hudson cluster |
Yes |
|
|
|
|
|
| DEVTEST-004 |
P1 |
Simple installation from a single Jar file or zip |
Yes |
|
|
|
May have a small set of dependencies as reasonable, so that installing it does not require fetching dozens of artifacts |
|
| DEVTEST-005 |
P1 |
Simple configuration |
Yes |
|
|
|
need to be able to use from hudson (hudson plugin ?) |
|
| DEVTEST-006 |
P2 |
Generates reports of test results in a standard format |
Yes |
|
|
|
e.g. JUnit report format, which can be integrated with Hudson |
|
| DEVTEST-007 |
P2 |
Easy to attach a debugger to a failing test for further analysis |
No |
|
|
|
|
| DEVTEST-008 |
P2 |
Easy to turn on logging as needed |
TBD |
|
|
|
|
| DEVTEST-009 |
P3 |
Easy to correlate logs with individual test cases |
Yes |
|
|
|
|
| DEVTEST-010 |
P3 |
Code coverage number |
No |
|
|
|
e.g. EMMA |
Design Document
Milestone Schedule
| Item # |
Date/Milestone |
Feature-ID |
Description |
QA/Docs Handover? |
Status |
Comments |
| 1.1 |
MS3 |
DEVTEST-001-Plugin Phase-1 |
Multiple GlassFish instances on a Single Hudson node |
No |
Done. |
Brown Bag Session. |
| 1.2 |
MS3 |
DEVTEST-001-Plugin Phase-2 |
Multiple GlassFish instances on multiple pre-configured Hudson nodes |
No |
Done |
MS3 Demo ; Deployed on test Hudson setup. Reviewed by couple of beta users. |
| 1.3 |
Probably, GF v3.2 |
DEVTEST-001-Plugin Phase-3 |
Multiple GlassFish instances on multiple dynamically allocated Hudson nodes |
No |
TBD
|
Hudson will need to be modified to provide full system allocation. This is still in the concept phase. |
| 2.1 |
MS2 |
DEVTEST-001-Ant Phase 1
|
Multiple GlassFish instances on a single node |
No
|
Done |
GF-Hudson-Ant README
The ant scripts that create the cluster, instances, startdas, kill instance, delete instance, stop instance, etc is complete. The ant script can either be used independently or can be invoked from within hudson. For more details look at the attached ant README .
|
| 2.2 |
|
DEVTEST-001-Ant Phase-2 |
Multiple GlassFish instances on multiple nodes |
|
|
| 3 |
MS3 |
DEVTEST-002 |
Portable and configurable for individual testing clusters |
No |
Done |
|
| 4 |
MS3 |
DEVTEST-003 |
Hudson integration to automate the dev test execution on a hudson cluster |
No |
Done |
|
| 5 |
MS3 |
DEVTEST-004 |
Simple installation from a single Jar file or zip |
No |
Done |
|
| 6 |
MS3 |
DEVTEST-005 |
Simple configuration |
No |
Done |
|
| 7 |
MS4 |
DEVTEST-006 |
Generates reports of test results in a standard format. . |
No |
Done |
Copy over and save the server logs for all the instances when the test execution is completed |
Task List
| Task |
Target Milestone |
Start |
End Date |
Owner(s) |
Feature ID |
Status / Comments |
|
