I looked the code in the repository, and code looks good. I can see that you are executing the JBITest.java through an ant target. I also noted the directory structure you created. I will also use the same package structure to ensure easy integration of the code.

During the meeting, you asked about what extra value my current work will add. May be I need to throw some light on this topic.  In the current setup,

1. We have only one .java file containing all the test cases. However, in future when there will be hundreds of test cases, we will need a better code organization mechanism to arrange our test cases.

2. Currently the ant 'test' target runs the test cases mentioned in this single java file. However, we should be able to convey to this ant 'test' target that we either want to run all the test cases, or just the selected test cases written in one or more .java files. 

3. The JBITest.java does not log the result of each test execution into any output file. Similarly just running the test cases is not enough. We need to code the criterion for test success/failure as  part of the test case itself and log the results appropriately.

4. We also need to decide on a common documentation template for our test cases. That's because just by reading the test case code, one can not understand the purpose of the test. This will also lead to the tracability of our test cases.

My idea of developing a framework will help in achieving the points mentioned above:

1. Developing and organizing the test cases

Framework will organize tests into "Test Groups". A test group will be a collection of tests that will serve a specific purpose. For example, there may be one called "Nightly Tests" that contains all the tests that should be run after each nightly deployment of GlassFish. There may be another called 'System Tests".

2.  Executing them in a selected manner.

The framework will use a parameter file to identify various test groups, each containing references to the classes that need to be run as well as the properties needed to run them. For example: instead of hardcoding the AdminBUI URL or File Upload location in each test class, the test classes will pick them from this parameter file.

3.  Directing the output into an XML format file.

The framework will store the output from each test into an XML file, so that the results can be viewed and analyzed in an external application. The test result will contain purpose of the test, tracability to the documented test case, and result of the each test alongwith the timestamp.

I am just trying to augment the test framework setup that we have in place, therefore I don't see any overlap between our work. Please go ahead with your selenium based JBI Upload test case development. Once I am done with the framework development, I will tweak your test cases to get executed through the framework. Once this is done I will also start automating the test cases.

Thanks,

Swarna Mishra