Return-Path: Delivered-To: apmail-ws-juddi-dev-archive@www.apache.org Received: (qmail 18509 invoked from network); 29 Oct 2008 16:20:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Oct 2008 16:20:47 -0000 Received: (qmail 42704 invoked by uid 500); 29 Oct 2008 16:20:52 -0000 Delivered-To: apmail-ws-juddi-dev-archive@ws.apache.org Received: (qmail 42683 invoked by uid 500); 29 Oct 2008 16:20:52 -0000 Mailing-List: contact juddi-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: juddi-dev@ws.apache.org List-Id: Delivered-To: mailing list juddi-dev@ws.apache.org Received: (qmail 42672 invoked by uid 99); 29 Oct 2008 16:20:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Oct 2008 09:20:52 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Oct 2008 16:19:34 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6F5D3234C249 for ; Wed, 29 Oct 2008 09:19:44 -0700 (PDT) Message-ID: <334711746.1225297184455.JavaMail.jira@brutus> Date: Wed, 29 Oct 2008 09:19:44 -0700 (PDT) From: "Jeff Faath (JIRA)" To: juddi-dev@ws.apache.org Subject: [jira] Created: (JUDDI-147) Create test data in the form of input XML files MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 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 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. --------------------------------------------------------------------- To unsubscribe, e-mail: juddi-dev-unsubscribe@ws.apache.org For additional commands, e-mail: juddi-dev-help@ws.apache.org