juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcos Vincius (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Updated: (JUDDI-147) Create test data in the form of input XML files
Date Mon, 05 Jan 2009 11:03:44 GMT

     [ https://issues.apache.org/jira/browse/JUDDI-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Marcos Vincius updated JUDDI-147:

    Attachment: marcosentities.zip

The atached zip file contains some UDDI entities in xml format.

> Create test data in the form of input XML files
> -----------------------------------------------
>                 Key: JUDDI-147
>                 URL: https://issues.apache.org/jira/browse/JUDDI-147
>             Project: jUDDI
>          Issue Type: Task
>    Affects Versions: 3.0
>            Reporter: Jeff Faath
>            Assignee: Jeff Faath
>             Fix For: 3.0
>         Attachments: marcosentities.zip
> In order to properly test the new version 3.0 code, a good amount of test data is required.
 The test data should be in the form of XML files that conform to the UDDI data structures.
 Data should be created that satisfies the input for the UDDI API calls - in particular the
Publish and Inquiry APIs.
> An example of important entities for publish API include: businessEntity, businessService,
bindingTemplate, and tModel.  At least 5 to 10 businesses should be created with associated
services and binding templates.  Additionally, tModels should be created that correspond to
category types and identifier types referred to by the entities.  It would be best if this
data was created to mimic real-world data.
> For the inquiry API, various find_* (find_business, find_service, etc.) files should
be created that test the many search metrics involved in the UDDI spec.  The "find qualifiers"
of these search files should vary to test all the features.  Search criteria should be designed
to return a specific portion of the data created for the publish API so that unit tests can
be easily coded.
> It is recommended that the UDDI v3 (http://uddi.org/pubs/uddi-v3.0.2-20041019.htm) specification
be consulted when creating this data.  Some very basic sample data has already been created
and is located under the org.apache.juddi.test package.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message