[jsr362-observers:] [jsr362-experts:] Re: The JSR 362 TCK on Pluto is open for business ...
- From: Werner Keil <
- Subject: [jsr362-observers:] [jsr362-experts:] Re: The JSR 362 TCK on Pluto is open for business ...
- Date: Sun, 27 Jul 2014 16:51:37 +0200
- List-id: <jsr362-experts.portletspec3.java.net>
Thanks, AFAIK I am committer in the Apache Portlet umbrella which Pluto
must be under, so I should be able to check out this repository and be able
to contribute there.
On Sun, Jul 27, 2014 at 10:03 AM, Martin Scott Nicklous <
> I added the JSR 362 TCK to the Apache Pluto project.
> In the EG call on Tuesday, I mentioned that I had generated skeleton code
> for the JSR 286 compatibility test cases from the test case assertions
> document. Over the past few days, I took this idea further and improved the
> code generation process in order to automatically generate complete test
> code for the JSR 286 method, field, and class signatures. This turned out
> better than expected, and we now have 2020 test cases in total, of which
> 1090 execute correctly against Pluto. The remaining tests fail because the
> test case code must be developed manually and has not yet been completed.
> However, the test portlets contain skeleton code for the remaining test
> If you want to help develop the remaining test cases, you would be most
> The TCK contains a generated test framework for the JSR286 compatibility
> portion of the TCK. The framework contains method signature testing code
> along with tests to be developed manually.
> Portlets whose names contains the string 'SIG' contain complete,
> automatically generated test code for the JSR 286 API signature tests.
> These portlets should not be changed manually. The signature tests execute
> correctly on Pluto.
> The remaining portlets contain skeleton code for test cases that must be
> implemented manually. Most of these tests fail, as the code has not yet
> been developed.
> View the portlet-tck_3.0/README.txt file for an overview and a usage
> The TCK code on Pluto was copied from the portletspec3 project on github.
> Going forward, the portlet-tck_3.0 directory on the Pluto project will be
> the home for the TCK. Further TCK development will take place on Pluto.
> Over the next few days, I plan to document the compatibility test
> assertions based on the JSR 286 specification document (the current tests
> are based on the JSR 286 API documentation). Once that is complete, I'll
> help implement the remaining TCK compatibility test cases.
> Mit freundlichen Grüßen, / Kind regards,
> Scott Nicklous
> WebSphere Portal Standardization Lead & Technology Consultant
> Specification Lead, JSR 362 Portlet Specification 3.0
> IBM Software Group, IBM Collaboration Solutions
> IBM Deutschland Research & Development GmbH / Vorsitzender des
> Aufsichtsrats: Martina Koederitz / Geschäftsführung: Dirk Wittkopp
> Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
> HRB 243294