Re: [Soaplite-devel] SOAP::Lite development - next release

[<mr...@za...>]

Yes. Local services are, of course, better - but cannot be counted on =20
being available all the time when someone is installing SOAP::Lite.

Google has a good websearch API, I believe. Amazon has one too. I =20
believe there is a National Weather Service one too. Things like this =20
might be a good way to test an install, as they've been around for =20
years, and are not likely to disappear in the near future. Of course, =20
nothing is 100%.

Maybe we could make the tests optional - and say what each test is =20
testing. That way, when 40% fail next year, I can see that X Y and Z =20
are untested because they failed, but features A B and C should still =20
work fine.

--Matthew

Quoting Robert Landrum <rla...@ao...>:

> Matthew Runo wrote:
>> Yes, the test suite ran upon install has been failing for some time =20
>>   now. I've been ignoring it, and --force installing. I vote to  =20
>> remove  it - add in a couple you know are live and go for it.
>>
>
> That's sort of the problem.  What is live, and what is going to be live
> in perpetuity.
>
> It's a trivial matter to test against local services, but more often
> than not, I find services written in Java, C#, etc, to be incompatible
> with the current SOAP::Lite implementation... And that just within my
> organization.  :(
>
> I found this...  http://www.xmethods.net/ilab/
>
> I haven't looked at the test suite, so I'm not sure how many these are
> actually being tested.
>
> Rob



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.