Mailing-List: contact axis-cvs-help@ws.apache.org; run by ezmlm
Precedence: bulk
Date: 27 Sep 2004 11:04:31 -0000
Message-ID: <20040927110431.61316.qmail@minotaur.apache.org>
From: damitha@apache.org
To: ws-axis-cvs@apache.org
Subject: cvs commit: ws-axis/c/tests/auto_build Readme.txt

damitha     2004/09/27 04:04:31

  Modified:    c/tests/auto_build Readme.txt
  Log:
  Readme.txt is updated to include how to automatcically test your services
  
  Revision  Changes    Path
  1.5       +33 -16    ws-axis/c/tests/auto_build/Readme.txt
  
  Index: Readme.txt
  ===================================================================
  RCS file: /home/cvs/ws-axis/c/tests/auto_build/Readme.txt,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- Readme.txt	15 Sep 2004 04:23:51 -0000	1.4
  +++ Readme.txt	27 Sep 2004 11:04:31 -0000	1.5
  @@ -1,7 +1,11 @@
   ##############################################################################
   
  -This folder contains auto build script for Axis C++ and basic regression test cases for the C/C++
  -Client Web Services Stack (CWSS). 
  +This folder contains auto build script for Axis C++ and basic regression test 
  +cases for the C/C++ Service/Client Web Services Stack. For each wsdl service is 
  +created and built and installed into the server.  Remeber to put your correct 
  +port type implementation class in the appropriate place described in the 
  +documentation. Normally you don't put this implementation file if your service 
  +is running in a remote server.
   
   ##############################################################################
   
  @@ -14,6 +18,12 @@
   testcases/wsdls/
    Contains the WSDL for the test cases.
   
  +testcases/server/
  + Contains the C and C++ service classes.
  + NOTES:
  +        Implementation class name of the wsdl PortType is taken
  +        from the port name of the wsdl file suffixing with .cpp/.c
  +
   testcases/client/
    Contains the C and C++ invocation clients.
    NOTES: Each client must have the same basename as the WSDL file
  @@ -23,10 +33,6 @@
   testcases/output/
    Contains the output of the client invocation expected result.
   
  -testcases/server/
  - Contains the server implementation of the binding (WAS 5.0.2). And
  - the ear file. 
  -
   ##############################################################################
   
   ENVIRONMENT VARIABLES
  @@ -83,36 +89,47 @@
   
   When you want to add a new test please be aware of the following simple steps.
   
  -1. Write the cpp file containing your main method of access and put
  +1. Put the wsdl you hope to test in
  +   testcases/wsdls
  +
  +2. Create the c/cpp file which has the name of the port type name of the wsdl
  +   and implement your service
  +
  +3. Write the c/cpp file containing your main method of access and put
      it in $AXISCPP_HOME/tests/auto-build/testcases/client/cpp
       NOTES: Each client cpp file must have the same basename as the 
       WSDL  file plus Client.
       Example: SimpleTypeArray.wsdl -> SimpleTypeArrayClient.c[pp]
   
  -2. Put the wsdl you hope to test in
  -   testcases/wsdls
  -
  -3. Add the server and port running the webservice in 
  +4. Add the server and port running the webservice in 
      testcases/platform/linux/test.config file. The format is
      <wsdl file name (without .wsdl part)>:host=<your host>
      <wsdl file name (without .wsdl part)>:port=<your port>
  +   Also give your APACHE2_PORT and APACHE_PORT in
  +   testcases/platform/linux/apache_ports.config file. Giving
  +   these information is very important as tests are first run
  +   using apache2 and then using apache. port in test.config
  +   is replaced with whatever on apache_ports.config file whenever
  +   the tests are run. Anyway you must initially give the port
  +   in test.config file as a initialization kind of value.
   
  -4. cd to auto_build and edit the build.sh file
  +5. cd to auto_build and edit the build.sh file
      according to your configure requirments.
      Run autoBuildCVS.sh
      This will first checkout from cvs and then build the source.
      Then generate samples from each wsdl.
  -   You will have a new folder creaed in testcases/build folder with the 
  -   same name as the client cpp file name.
  +   You will have two folders created in testcases/build folder for service
  +   and client. Each have the wsdl filename suffixed with .cpp_server and 
  +   .cpp_client respectively.
      First time you should get run FAIL message. That's because you still
      does not have a .out file indicating your expected result. We will
      create this in the next step
   
  -5. in testcases/build/<automaticall creaed your client folder> you will
  +6. in testcases/build/<automaticall creaed your client folder> you will
      see a file named <Your client file name>.cpp.out
      Copy this file into testcases/output
   
  -6. Next time you should get your test passed
  +7. Next time you should get your test passed
      with SUCCESS.
      This time the build/<Your client file name>.cpp.out matchs correctly
      with the pre created output in testcases/output