Hi all.
I tried but could not find any active enough project repositories so
I
prepared a Mercurial repository at 'https://bitbucket.org/jurko/suds'
containing some of my patches - for now mostly concentrating on
preparing a more detailed test suite as I research suds. For other
topics I'd like to change/add in the suds library itself - I'll post
separate messages to the mailing list.
--- Update on what has been done so far in my suds library project fork.
* Cleaned up the test suite a bit.
* Separated automated tests and 'quasi-tests' that are actually
just Python scripts someone could use to manually test suds by tweaking
them and reading through their output.
* Ported the one existing automated unit test script to use the
pytest unit test framework (better infrastructure + fixes problems with
running the test from an unexpected folder or having another set of suds
library sources already on the Python module search path, e.g. installed).
* Fixed DateTimeTest.testOverflow test code problems caused by that
test case depending on a global Timezone.LOCAL setting left behind by
other tests.
* Added additional tests.
* Added support for operations taking choice parameters (based on a
patch by michaelgruenewald & bennetb01 attached to ticket #342).
* Code base compatible with Py3 patches hosted at
'https://bitbucket.org/bernh/suds-python-3-patches' and all tests seem
to run and no manually tested code triggered any problems in the
following scenarios:
* Python 2 without Py3 patches applied.
* Python 2 with Py3 patches applied.
* Python 3 with Py3 patches applied.
* Corrected accessing suds.xsd.sxbase.SchemaObject subitems by index
(see 'http://fedorahosted.org/suds/ticket/420').
--- Some questions for whomever can offer assistance. :-)
Anyone want to contribute his own work on suds to this or wants to
integrate this into some already existing and actively developed code base?
Anyone wants to help write additional tests? Or has his own tests
tucked away somewhere that he would like to contribute?
Any suggestions on what would be the easiest way to implement the
following test types:
* Tests for constructing SOAP requests.
* Tests for parsing SOAP responses.
* Tests requiring an actual running web service.
* For example, I want to add support for connecting to a web
service using HTTPS with client certificate authentication (already
implemented and used in an actual end-user application using suds but
I'd like to push this change back to suds and add tests for it).
* Any suggestions on the best lightweight framework for
implementing such a test web service?
--- Next steps.
I'll prepare a new forked suds distribution now containing all the
changes (need it internally so other projects do not depend on suds
library development sources). If there is any interest I can publish it
publicly (PyPI?). Disclaimer: I would like it best if I did not need to
do a separate distribution and could get all of this integrated into the
main development repository but it seems I can not wait for that and
need some 'clean milestones' developed at a much greater pace than
observed in the current official development.
Best regards,
Jurko Gospodnetić