see comments below:
_______________________________________
Adrian Dick ([EMAIL PROTECTED])
"sanjaya singharage" <[EMAIL PROTECTED]> wrote on 19/01/2005 08:52:47:
>
> ----- Original Message -----
> From: "Adrian Dick" <[EMAIL PROTECTED]>
> To: "Apache AXIS C Developers List" <[email protected]>
> Sent: Wednesday, January 19, 2005 2:25 PM
> Subject: Re: Ant test framework - running a test
>
>
> >
> >
> >
> >
> > If the problem is only a difference in expected output and actual
output
> > then there are several potential causes:
> >
> > 1) The test is genuinely failing - but you're obviously
confident
> > this isn't the case
>
> I manually checked the .out file after running the rest and from that the
> test is passing.
>
> > 2) A change within the runtime (or generated stubs) resulting in
> > differences in the output, without expected output being updated -
if
> > this is the case you will need to confirm these changes are correct
> > changes, before updating the expected output.
>
> what do you mean here by a change within the runtime?
A good example here is when testing exceptions or faults. Recently,
various points in the runtime have been changed to provide more information
in exceptions. If the exception content is being output, then this will
obviously have an effect on the test output.
>
> > 3) The test client has been changed in some way that affects the
output,
> > again without the expected output being updated.
> >
>
> In other words if a test fails the first thing to do is to check the
output
> file and see whether the test actually did succeed and that the two
outputs
> are not matching?
Basically. Unfortunately, the Axis runtime hasn't quite reached a
sufficiently stable point for us to guarantee a failing tests is genuinely
highlighting a code regression. But the closer we get to a release the
more stable it should become.
>
> sanjaya.
> > Note: I have recently seen problems where the test client make use of
> both
> > cout and printf, and the printed statements get out of sequence. The
fix
> > to this is quite simple - change all printfs to couts, I have already
done
> > this for a number of tests, though not all.
> >
> > Regards,
> > Adrian
> > _______________________________________
> > Adrian Dick ([EMAIL PROTECTED])
> >
> >
> > "sanjaya singharage" <[EMAIL PROTECTED]> wrote on 19/01/2005
> 04:55:01:
> >
> > > Finally it says
> > >
> > > [echo] Calculator - Client Execution - PASSED
> > >
> > > The problem is that the Calculator.out file does not match
> > > Calculator.cpp.out file. When .out file is copied over .cpp.out file
the
> > > test passes. what could be the reason for this?
> > >
> > > sanjaya.
> > >
> > > ----- Original Message -----
> > > From: "Manohar K Chintala" <[EMAIL PROTECTED]>
> > > To: "Apache AXIS C Developers List" <[email protected]>
> > > Sent: Tuesday, January 18, 2005 6:47 PM
> > > Subject: Re: Ant test framework - running a test
> > >
> > >
> > > >
> > > >
> > > >
> > > >
> > > > Hi Sanjaya,
> > > >
> > > > Yes, those are the two files that are compared to check whether a
test
> > > > suceeded or not. We have run ant framework on windows and it works
for
> > us
> > > > without any problem.
> > > >
> > > > Below are the contents of axiscpp.conf file in my system. You can
try
> > > > changing \ to / in the axiscpp.conf file entries.
> > > >
> > > > #Available directives are as follows:
> > > > #
> > > > # ClientLogPath: The path to the client log
> > > > # ClientWSDDFilePath: The path to the client wsdd
> > > > # Transport_http: The HTTP transport library
> > > > # XMLParser: The xml parser library
> > > > #
> > > > ClientLogPath:f:\IBM\CWSC\logs\AxisClientLog
> > > > ClientWSDDFilePath:f:\IBM\CWSC\client.wsdd
> > > > Transport_http:f:\IBM\CWSC\bin\AxisTransport.dll
> > > > XMLParser:f:\IBM\CWSC\bin\AxisXMLParser.dll
> > > >
> > > >
> > > > Regards
> > > > Manohar
> > > > --------------------------------------------------
> > > > Manohar Kumar.Ch
> > > > IBM C/C++ Web Services Client
> > > > India Software Labs,III floor, Golden Enclave,
> > > > Aiport Road, Bangalore-560017
> > > > Ph:- 91-80-25094304
> > > > internet id: [EMAIL PROTECTED]
> > > >
> > > >
> > > >
> > > > "sanjaya
> > > > singharage"
> > > > <[EMAIL PROTECTED]
> > To
> > > > rce.lk> "Apache AXIS C Developers
List"
> > > > <[email protected]>
> > > > 01/18/2005 05:41
> > cc
> > > > PM
> > > >
> > Subject
> > > > Re: Ant test framework -
> running
> > a
> > > > Please respond to test
> > > > "Apache AXIS C
> > > > Developers List"
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > I think something is finally working. Still the dispalyAllResults
say
> > the
> > > > client execution failed. But everything else indicates that the
test
> > was
> > > > successful.
> > > >
> > > > The problem seems to be how the path is written for the
> > xmlparserlibrary
> > > > etc. in axiscpp.conf specified from executeTest.xml.
> > > >
> > > > The following axiscpp.conf worked for me..
> > > >
> > > > #Available directives are as follows:
> > > > #
> > > > # ClientLogPath: The path to the client log
> > > > # ClientWSDDFilePath: The path to the client wsdd
> > > > # Transport_http: The HTTP transport library
> > > > # Transport_smtp: The SMTP transport library
> > > > # XMLParser: The xml parser library
> > > > #
> > > >
> > >
> >
>
ClientLogPath:D:\san\works\checkouts\head\ws-axis\c/../../../obj/test/genera
> >
> > > ted/cpp/Calculator/ClientLog
> > > >
> > > >
> > >
> >
>
#Transport_http:D:\san\works\checkouts\head\ws-axis\c/../../../obj/bin/AxisT
> >
> > > ransport.dll
> > > >
> > > >
> > >
> >
>
Transport_http:D:\san\works\checkouts\obj\package\axis-c-1.4.0-Win32-bin\bin
> >
> > > \axis2_transport.dll
> > > >
> > > >
> > >
> >
>
#XMLParser:D:\san\works\checkouts\head\ws-axis\c/../../../obj/bin/AxisXMLPar
> >
> > > ser.dll
> > > >
> > > >
> > >
> >
>
XMLParser:D:\san\works\checkouts\obj\package\axis-c-1.4.0-Win32-bin\bin\Axis
> >
> > > XMLParser.dll
> > > >
> > > > is the mixed / and \ path causing the problem? Is the ant test
> > framework
> > > > being run on a wind0ws box? If so I wonder what is the problem in
my
> > > > system.
> > > >
> > > > Calculator.out and tcpm.req and tcpm.res all indicate that the test
> was
> > > > successful. Why does dispalyAllResults say the client execution
> failed?
> > > >
> > > > I edited
> > > >
> > >
> >
>
\obj\package\axis-c-1.4.0-Win32-bin\tests\auto_build\testcases\output\Calcul
> >
> > > ator.cpp.out
> > > > to match obj\test\generated\cpp\Calculator\Calculator.out but
still
> > > > "execution failed". Are these the two files that are compared to
check
> > > > whether a test suceeded?
> > > >
> > > > thanks.
> > > > sanjaya.
> > > >
> > > > ----- Original Message -----
> > > > From: sanjaya singharage
> > > > To: Apache AXIS C Developers List
> > > > Sent: Tuesday, January 18, 2005 3:31 PM
> > > > Subject: Re: Ant test framework - running a test
> > > >
> > > > The command follows..
> > > >
> > > > ant -f
> > > test.xml -Ddir.xmlParser="D:\installations\xerces-c2_2_0-win32\bin"
> > > > -Dtest.name=Calculator
> > > >
> >
-Ddir.release="D:\san\works\checkouts\obj\package\axis-c-1.4.0-Win32-bin"
> > > >
> > > > sanjaya.
> > > > ----- Original Message -----
> > > > From: James Jose
> > > > To: Apache AXIS C Developers List
> > > > Sent: Tuesday, January 18, 2005 3:17 PM
> > > > Subject: Re: Ant test framework - running a test
> > > >
> > > >
> > > > Sanjaya,
> > > >
> > > > oops...pressed send button before completing the draft
> > > >
> > > > Can u send the command that u used to run a test
> > > >
> > > > Regards
> > > > James
> > > > --------------------------------------------------
> > > > James Jose
> > > > Messaging Clients Team, WMQDDC
> > > > IBM Software Labs, India
> > > > Direct: 91-80- 25094331 Ext :2331
> > > > E-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > > >
> > > >
> > > > James
> > > > Jose/India/[EMAIL PROTECTED]
> > > >
> > > >
> > To
> > > > 18/01/2005 14:40 "Apache AXIS C Developers
> List"
> > > > <[email protected]>
> > > >
> > cc
> > > > Please respond to
> > > > "Apache AXIS C
> > Subject
> > > > Developers List" Re: Ant test framework -
> > running a
> > > > test
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Sanjaya,
> > > >
> > > > Can u send the command that u
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Regards
> > > > James
> > > > --------------------------------------------------
> > > > James Jose
> > > > Messaging Clients Team, WMQDDC
> > > > IBM Software Labs, India
> > > > Direct: 91-80- 25094331 Ext :2331
> > > > E-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > > >
> > > > "sanjaya singharage"
> > > > <[EMAIL PROTECTED]>
> > > >
> > > >
> > To
> > > > 18/01/2005 12:16 "Apache AXIS C
Developers
> > > > List"
> > > >
> <[email protected]>
> > > > Please respond to
> > cc
> > > > "Apache AXIS C Developers List"
> > > >
> > Subject
> > > > Re: Ant test framework
-
> > > > running a test
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > It failed with this property included. that's what's confusing me.
> > > >
> > > > sanjaya.
> > > > ----- Original Message -----
> > > > From: James Jose
> > > > To: Apache AXIS C Developers List
> > > > Sent: Tuesday, January 18, 2005 12:11 PM
> > > > Subject: Re: Ant test framework - running a test
> > > >
> > > >
> > > > Hi,
> > > > I think if u pass xmlparser info then this problem will be
solved.
> > > > So include -Ddir.xmlParser=[directory of xmlparser] also in the
ant
> > > > command.
> > > >
> > > > Regards
> > > > James
> > > > --------------------------------------------------
> > > > James Jose
> > > > Messaging Clients Team, WMQDDC
> > > > IBM Software Labs, India
> > > > Direct: 91-80- 25094331 Ext :2331
> > > > E-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > > > "sanjaya singharage"
> > > > <[EMAIL PROTECTED]>
> > > >
> > > >
> > To
> > > > 17/01/2005 18:10 "Apache AXIS C
Developers
> > > > List"
> > > >
> <[email protected]>
> > > > Please respond to
> > cc
> > > > "Apache AXIS C Developers List"
> > > >
> > Subject
> > > > Re: Ant test framework
-
> > > > running a test
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Still having problems. Finally got it working to generate the
source
> > and
> > > > compile.
> > > > When running the calculator sample the execution fails. The output
of
> > the
> > > > Calculator.out file is...
> > > >
> > > > Sending Requests to Server http://localhost:13260/axis/Calculator
> > .......
> > > >
> > > > Exception : DLOPEN FAILED in loading parser library
> > > >
> > > > When I run the client separately on the command line the test
> > succeeds.
> > > > What
> > > > am I missing?
> > > >
> > > > sanjaya.
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "Samisa Abeysinghe" <[EMAIL PROTECTED]>
> > > > To: "Apache AXIS C Developers List" <[email protected]>
> > > > Sent: Tuesday, January 11, 2005 4:51 PM
> > > > Subject: Re: Ant test framework - running a test
> > > >
> > > >
> > > > > The problem is that when ant is run with test.xml, it is trying
to
> > use
> > > > > the release folder wsdl2ws.jar wihtout -bin suffix.
> > > > > I think it would work if we suffix use of dir.release in test
> > related
> > > > files.
> > > > >
> > > > > Thanks,
> > > > > Samisa...
> > > > >
> > > > >
> > > > > On Tue, 11 Jan 2005 10:40:10 +0000, Adrian Dick
> > > <[EMAIL PROTECTED]>
> > > > wrote:
> > > > > >
> > > > > >
> > > > > > The packaging process appends '-src' and '-bin' to the end of
> > > > dir.release
> > > > > > when creating a source and binary package respectively. So,
> > > modifying
> > > > the
> > > > > > property files would not have the effect you're hoping for.
> > > > > >
> > > > > > _______________________________________
> > > > > > Adrian Dick ([EMAIL PROTECTED])
> > > > > >
> > > > > > Andrew Perry2/UK/[EMAIL PROTECTED] wrote on 11/01/2005 09:50:42:
> > > > > >
> > > > > > >
> > > > > > > I generally call the ant -f test.xml -Ddir.release=<path to
> > > package>
> > > > > > rather
> > > > > > > than change the properties file. I'm not too sure if/how the
> > > > build.xml
> > > > > > uses
> > > > > > > the dir.release property so cannot comment safely on
altering
> > the
> > > > > > > properties file, unless it is only for the test run in which
> > case
> > > > there
> > > > > > is
> > > > > > > no problem.
> > > > > > >
> > > > > > > Adrian any comments on what the impact of changing
dir.release
> > > > propery
> > > > > > > would have on the build/packaging process?
> > > > > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Andrew Perry
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
>
>
