|
Last update : May 2 2001
Home
Jakarta Commons
About
News
Features
Goals
Changes
Todo
Contributors
Contributing
License
Downloads
Downloads
User Guides
Architecture
Installation
Installing Ant
Installing Sample
Configuration
Writing Test Case
Servlet Sample
Ant integration
Servlet Engines
API Reference
Support
CVS
Bug database
Mailing lists
FAQ
|
Developers assigned to tasks |
|
medium severity tasks |
- [docs]
Write a tutorial that shows how to test EJBs.
- [samples]
Add a sample that shows how to test EJBs.
- [design]
Add support for testing custom JSP Taglibs (suggested by Sohail Aslam) +
tutorial + sample
- [design]
Add support for testing Servlet API 2.3 Filters.
(assigned to VMA)
- [design]
Provide support for easier testing of EJBs by writing an EJB Redirector
(which is a EJB Session Bean) so that it is possible to test EJB methods
that uses EJB container API like security checks, transaction, JNDI
calls, ... (requested by notyy).
(assigned to BNA)
|
low severity tasks |
- [docs]
Write a Cactus integration tutorial for JBuilder 4.
- [docs]
Write a Cactus integration tutorial for VAJava 3.5.
- [build]
Add Ant scripts to support WebLogic 6.0.
- [code]
Handle
getRealPath() , getPathTranslated() in the
ServletRedirectorRequest class.
- [code]
Add API in
ServletTestRequest to send data to the URL
connection output stream. This is to easily test code that sends bytes
of data as POST data to the servlet (requested by Daniel Cohen and
custommonkey).
- [code]
Automatically add the query string parameters defined when using the
ServletTestRequest.setURL() API to the list of parameters
passed to the server redirector, so that it won't be necessary to call
ServletTestRequest.addParameter() for each of these
parameters.
- [code]
Check why zipped distributable files have a mode of 644 on unix systems
(it should rather be 755). Thanks to Jason Crickmer.
- [docs]
Add a FAQ entry for explaining unit testing of persistent sessions.
|
wish severity tasks |
- [code]
Create a Cactus Doclet. This will introduce new javadoc tags (like the
EJBDoclet) that will be used by the javadoc command
to do several things : generate test classes and test methods, generate
richer documentation. Indeed, the best documentation for a method is
it's test methods that show how to use it effectively. So maybe we could
append to the HTML javadoc for a method the java test method code as an
example.
- [code]
Integration for Netbeans by integration with the Netbeans XTest module.
- [code]
Look at JXUnit to
see if an integration with Cactus can be done (proposed by Will Sargent).
|
|
|