Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 70320 invoked by uid 500); 28 Sep 2001 15:46:13 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 70298 invoked from network); 28 Sep 2001 15:46:12 -0000 Message-ID: <3BB49B6B.9E835ECF@apache.org> Date: Fri, 28 Sep 2001 11:46:51 -0400 From: Berin Loritsch X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Axis Development Subject: Junit testing of Wsdl2java Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I am in the process of creating automated testing of the generated files from Wsdl2java using JUnit. The process is somewhat trying as it is difficult to get the compiler to compile the classes. I got past that part just now by dynamically creating an Ant project with one task. The tests that are required are "deploy" and undeploy. There are also some sanity checks that must be made: The test must use reflection to determine that the methods are there with the expected signatures. The test must call the SOAP methods to ensure that the deployment was correct. What I need help with is determining what exactly is expected. Because this is a test, I want what is expected--so that if we get an unexpected result, we can flag it right away. I plan on using Avalon's ExcaliburTestCase because it allows for certain parts to be called once during the life of the test (i.e. source and class file generation). It also allows me to easily configure the test and run iterations based on config data. Plus, if we decide to componentize the Axis server, it will allow much easier integration. The approach I will take is to figure out what Wsdl2java does, and test for that. The problem is if the results are wrong then the test is wrong.