Improve and streamline testcase development in Jetspeed
-------------------------------------------------------
Key: JS2-309
URL: http://issues.apache.org/jira/browse/JS2-309
Project: Jetspeed 2
Type: Improvement
Components: Testing
Versions: 2.0-M4
Reporter: Scott T Weaver
Assigned to: Scott T Weaver
Fix For: 2.0-M4, 2.0-FINAL
I want to make it easier on us to write high-performance test cases against
Jetspeed components. Currently we rely on sections of and in some cases the
entire Jetspeed Spring engine to initialize and run our tests. I have read
articles advising * NOT * to use this approach inside your test cases and that
you should hand-assemble the components within the test cases themselves. We
also have some clunky test case inheritance hierarchies (I will take the blame
for that) that initialize more than we need in most cases. What I am doing to
solve this is to, instead of using abstract test cases, put together small set
"TestHelper" components that have there own setUp(0 and tearDown() methods that
perform specific functions such as initialize a datasource pool and properly
initializing OJB, etc. The datasource and OJB helpers are already in place and
I have them working in the registry tests with very little change to the test
cases themselves.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
