[
https://issues.apache.org/jira/browse/JUDDI-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665845#comment-13665845
]
Alex O'Ree commented on JUDDI-583:
----------------------------------
Personally, I'd like to see this is a packaged jar file that reads from a
properties file or uddi.xml file along side of it (has to be outside of the
jar). Execute with something like java -jar UDDI-TCK.jar
Since many of the UDDI endpoints are "optional", we'll need a way to toggle
tests for the specific endpoints.
And a way to designate an authentication method, and a way to provide the
usernames and passwords for the necessary accounts.
Finally, after running, we need to confirm that there is a net zero effect on
the registry. I.e. no businesses or tmodels are left behind. Everything created
by the tck should be deleted. (I'm pretty sure I'm guilty on that one)
> Productize the TCK test suite
> -----------------------------
>
> Key: JUDDI-583
> URL: https://issues.apache.org/jira/browse/JUDDI-583
> Project: jUDDI
> Issue Type: Improvement
> Reporter: Alex O'Ree
> Assignee: Kurt T Stam
>
> Productize and advertise on the website the usefulness and versatility of the
> TCK test suite. It should be usable as a conformance tool for any UDDI
> registry.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
