I added test modules for the additional tests gleaned from the JSR 286 specification to the TCK. The test case definitions should now be pretty much complete with the exception of the request dispatcher tests, which are still to be defined.
These are checked in at the Pluto git repository, located at: https://git-wip-us.apache.org/repos/asf/portals-pluto.git The spec chapter "PLT.19 Dispatching Requests to Servlets and JSPs" contains nearly 1/3 of the total defined test assertions in the JSR 286 specification. There are many detailed assertions concerning individual methods of the HTTPServletRequest and HTTPServletResponse objects. Since the assertions are fairly repetitive and regular, I see a possibility to generate more code than for previous modules. I am going to try to generate code and implement the request dispatcher tests this week. I also checked in the CSV files containing the raw assertion text, which is better for programmatic processing in case anyone else wants to try a hand at code generation for some of the other modules. These are located in the "portlet-tck_3.0/src/main/javadoc/doc-files" directory. There is also a "JSR362Assertions.pdf" file in that directory, but it is outdated. Once all of the assertions are defined, I'll update it. If anyone wants to help with the TCK implementation, you would be more than welcome. If you start working on a module, I suggest that you let people know what module are working on through a post to the pluto-dev mailing list, so that others know which modules are actively being worked on. Note that portlets whose class name contains the string "_SIG_" contain API signature tests that were generated programmatically. These should not be changed manually. regards, Scott
