DUNLIN RC1 testing

Hi Matthew,

Just been giving the release candidate you sent me a spin
and having a
few small problems. I can easily fix what I've seen but I'm
a little
confused about where to do it. I thought we released out of
head but
head doesn't seem to be at 1.2.2.

Here are  the things I'm seeing so far.

Linux:
  tests/SCA/phpunit/TestSuite.php
     ln 407 - requires SoapBinding rather than SOapBinding

Windows
   All of the phpt tests failed (am still investigating -
must be
something wrong with my environment)


I think we need to fix the project README as if refers to
the DEV-
BRANCH file which is not shipped.

More later

Simon


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

I'm still having problems with my Windows environment. All
of my phpt
tests fail with empty output files. Anyone any ideas?

Anyhow here's what I found...

Linux:
  FC6
  PHP 5.2.0

  tests/SCA/phpunit/TestSuite.php
     ln 407 - requires SoapBinding rather than SOapBinding

  examples/SCA/helloworldscajsonrpc/
     There is a issue with the case of Helloworld.php. The
index page
refers to
     it as HelloWorld.php. Best to be accurate.

  examples/SDO/rss-media missing

Windows
  XP SP2
  PHP 5.2.0

  All of the phpt tests failed (am still investigating -
must be
something wrong with my environment)

General
  README
    - sort out reference to DEV_BRANCH
    - Would be worth noting that we distribute examples and
they end
up in
       test/SCA_SDO/examples
       copying this dir to htdocs gives allows you to read
about/try
SCA and SDO examples.

  There is a new dependency, via PHP, on open ssl in the
tests (deep
joy - that kept me entertained for a while - not SCA-SDOs
fault
though). It would be useful to note somewhere  what 
extensions we
expect to be turned on to get a clear test run.
        sdo
        libxml
        soap
        json
        xmlrpc
        openssl
        curl
        pdo + you favourite driver for the DAS tests

     Having these tests fail because the extension is not
enabled in
valid but not an SCA_SDO problem. I could add a note to the
web site
and/or README ?

   We should have an index.html page in the examples dir
point to SDO
and SCA index pages.
   We should have in index.html in examples/DAS for
completeness to
explain what's going on

  Remove interop tests from
     SCA_SDO/tests/AllTests.php
     We don't ship these test (still useful for local
testing though)

Can you tell me where I should put fixes?

Regards

Simon


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

simonslawsgooglemail.com wrote:
> I'm still having problems with my Windows environment.
All of my phpt
> tests fail with empty output files. Anyone any ideas?

What happens if you run the generated php scripts manually?

>   There is a new dependency, via PHP, on open ssl in
the tests (deep
> joy - that kept me entertained for a while - not
SCA-SDOs fault
> though). 

Not sure what you mean by "via PHP". I know that
the ebaysoap binding 
has a dependency on openssl - and I did add a check to that
binding to 
make sure openssl is loaded.  Are you talking about
something else?

It would be useful to note somewhere  what  extensions we
> expect to be turned on to get a clear test run.
>         sdo
>         libxml
>         soap
>         json
>         xmlrpc
>         openssl
>         curl
>         pdo + you favourite driver for the DAS tests
> 

A good way to do this is to add a check to the SKIPIF
section of the 
test, so that it outputs an explanatory message if the
required 
extension is not available.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

On 15 Jun, 12:31, Caroline Maynard <c...php.net> wrote:
> simonsl...googlemail.com wrote:
> > I'm still having problems with my Windows
environment. All of my phpt
> > tests fail with empty output files. Anyone any
ideas?
>
> What happens if you run the generated php scripts
manually?
It turned out to be a Release vs Debug thing.
>
> >   There is a new dependency, via PHP, on open ssl
in the tests (deep
> > joy - that kept me entertained for a while - not
SCA-SDOs fault
> > though).
>
> Not sure what you mean by "via PHP". I know
that the ebaysoap binding
> has a dependency on openssl - and I did add a check to
that binding to
> make sure openssl is loaded.  Are you talking about
something else?
No, that's it. We require certain things to be loaded into
PHP so it
would be useful to say in the docs that some tests will fail
if you
don't have the right things loaded. It's OK that they fail
but it's
not our fault. Good that the tests bindings are kind enough
to tell
you.
>
> It would be useful to note somewhere  what  extensions
we
>
> > expect to be turned on to get a clear test run.
> >         sdo
> >         libxml
> >         soap
> >         json
> >         xmlrpc
> >         openssl
> >         curl
> >         pdo + you favourite driver for the DAS
tests
>
> A good way to do this is to add a check to the SKIPIF
section of the
> test, so that it outputs an explanatory message if the
required
> extension is not available.
Not sure about this. I was specifically thinking about the
unit tests
which blow up if the right extensions are not available but
probably
useful to see that as if they don't show an error people
might think
all of the features are availalble when they aren't.

Simon


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

simonslawsgooglemail.com wrote:

> On 15 Jun, 12:31, Caroline Maynard <c...php.net> wrote:
>> simonsl...googlemail.com wrote:
>>>   There is a new dependency, via PHP, on open
ssl in the tests (deep
>>> joy - that kept me entertained for a while -
not SCA-SDOs fault
>>> though).
>> Not sure what you mean by "via PHP". I
know that the ebaysoap binding
>> has a dependency on openssl - and I did add a check
to that binding to
>> make sure openssl is loaded.  Are you talking about
something else?
> No, that's it. We require certain things to be loaded
into PHP so it
> would be useful to say in the docs that some tests will
fail if you
> don't have the right things loaded. It's OK that they
fail but it's
> not our fault. Good that the tests bindings are kind
enough to tell
> you.
>> It would be useful to note somewhere  what 
extensions we
>>
>>> expect to be turned on to get a clear test
run.
>>>         sdo
>>>         libxml
>>>         soap
>>>         json
>>>         xmlrpc
>>>         openssl
>>>         curl
>>>         pdo + you favourite driver for the DAS
tests
>> A good way to do this is to add a check to the
SKIPIF section of the
>> test, so that it outputs an explanatory message if
the required
>> extension is not available.
> Not sure about this. I was specifically thinking about
the unit tests
> which blow up if the right extensions are not available
but probably
> useful to see that as if they don't show an error
people might think
> all of the features are availalble when they aren't.

By "unit tests" do you mean phpunit or phpt?
People who are used to pear 
packages are likely to run the tests by something like:

pecl run-tests -r

so if we had the SKIPIF sections I'm suggesting, then they
would see a 
message, for  example:

SKIP SCA ebaysoap test [tests/SCA/phpt/nnn.phpt] (reason:
ebaysoap SCA 
binding requires openssl extension)

I would find that more helpful (and maintainable) than a
para in some 
docs somewhere that I probably haven't read.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

Simon,
the place to fix things is in DUNLIN. Once that is right,
then I will
move the code across to HEAD, create the release, and make
the new
branch.

Please go ahead and fix anything you want to, then when you
have
finished let me know what's left. I should have made more
effort to
catch the case-related one that shows on Linux so I will
sort out my
Linux system so I could have caught that one - please go
ahead and fix
it though.

I agree with Caroline's suggestion:
> so if we had the SKIPIF sections I'm suggesting, then
they would see a
> message, for  example:

> SKIP SCA ebaysoap test [tests/SCA/phpt/nnn.phpt]
(reason: ebaysoap SCA
> binding requires openssl extension)

> I would find that more helpful (and maintainable) than
a para in some
> docs somewhere that I probably haven't read.

Suppose a user wants to run the tests but doesn't intend to
use the
ebaysoap binding then they don't need to load the extension.
We should
not force them to load the extension just to run the tests.

In the meantime I will put the release up in the files
section of this
google group.

Matthew


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

SCA_SDO-1.2.2.tgz - the version that Simon has been using
above, no
fixes yet - is now in the files section.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

On 18 Jun, 10:56, Matthew Peters <matthew.f.pet...googlemail.com>
wrote:
> SCA_SDO-1.2.2.tgz - the version that Simon has been
using above, no
> fixes yet - is now in the files section.

OK, I've done the easy fixes in DUNLIN. I've also overhauled
the
installation instruction so if people could go and review
them that
would be good.

 Things left to do If any one fancies taking a look

1/ examples/SCA/helloworldscajsonrpc/ there is a issue with
the case
of Helloworld.php. For some reason I can't spot what I
thought was
wrong with this one.

2/ examples/SDO/rss-media missing. It's in the branch so we
either
need to ship it or remove the example from the
examples/SDO/index.htm.
Is there a good reason why we don't ship it?

3/ I haven't done any of the suggested skipping stuff in the
unit
tests. Not essential for this release but a nice to have.

4/ phpt tests 4 and 13 fail for me.  I'm looking at 4 now.


001+ Warning: SDO_DAS_XML::create():
php_network_getaddresses:
getaddrinfo failed: No such host is known.  in
C:simonProjects
Tuscanyphpbranch-buildpeclsdoSCABindingssoap
ServiceDescriptionGenerator.php on line 65
002+
003+ Warning: SDO_DAS_XML::create(http://schemas.xmlso
ap.org/wsdl/):
failed to open stream: No such file or directory in
C:simonProjects
Tuscanyphpbranch-buildpeclsdoSCABindingssoap
ServiceDescriptionGenerator.php on line 65
004+
005+ Warning: SDO_DAS_XML::create(): I/O warning : failed to
load
external entity "http://schemas
.xmlsoap.org/wsdl/" in C:simonProjects
Tuscanyphpbranch-buildpeclsdoSCABindingssoap
ServiceDescriptionGenerator.php on line 65
006+
007+ Fatal error: Uncaught exception
'SDO_DAS_XML_ParserException'
with message 'SDO_DAS_XML::create - Unable to parse the
supplied xsd
file
008+ 1 parse error(s) occurred when parsing the file
'C:simonProjects
Tuscanyphpbranch-buildpeclsdoSCABindingssoap/soap/
2003-02-11.xsd':
009+ 1. xmlSAXUserParseFile returned an error -1
010+ ' in
C:simonProjectsTuscanyphpbranch-buildpeclsdoSCA
BindingssoapServiceDescriptionGenerator.php:65
011+ Stack trace:
012+ #0
C:simonProjectsTuscanyphpbranch-buildpeclsdoSCA
BindingssoapServiceDescriptionGenerator.php(65):
SDO_DAS_XML::create(Array)
013+ #1
C:simonProjectsTuscanyphpbranch-buildpeclsdotestsSC
A
phpt04.php(7):
SCA_Bindings_soap_ServiceDescriptionGenerator::generateDocum
entLiteralWrappedWsdl(Object(SCA_ServiceDescription))
014+ #2 

13 (bug 10049) is a memory leak being reported

Regards

Simon



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "phpsoa" group.
To post to this group, send email to phpsoagooglegroups.com
To unsubscribe from this group, send email to
phpsoa-unsubscribegooglegroups.com
For more options, visit this group at http://
groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---