#2867: Add native Selenium support to django.test framework.
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Status: new | Component: Unit test
system
Version: | Resolution:
Keywords: selenium | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------------------------+-----------------------------------
Comment (by anonymous):
Important update.
After months of trying to make Selenium not break on me every week myself
and another developer at OSAF wrote a replacement. It's 100% js and python
and will be announced publicly sometime in March, hopefully with a
presentation at OSCON.
I'll be happy to create another ticket after March to add support for that
system rather than Selenium but I won't be able to add Selenium support in
this ticket.
Notes for whoever may write this:
The biggest problem someone else implementing this will run in to is
interfacing with the Selenium RC server, and in turn interfacing with the
browserbot through the server to get useful information about failures.
The SeleniumRC server is in java and fairly unflexible.
It also doesn't support a real RPC protocol for the remote client library,
all commands to the RC are communicated over URL parameters passed to the
proxy and there isn't a very steady communication workflow between the RPC
client and the server OR the RC server and the browserbot. The
architecture makes it very pritle and nearly impossible to debug,
especially in a continuous environment like an automated build/test
system.
Also, you'll want to just maintain your own branch of the python remote
client library. The method calls which translate into browser actions are
all statically defined in the module, so any custom methods in the
user_extensions won't work. It's about 8 lines to write a real dynamic
wrapper in __getattr__ to call remote selenium methods, but they won't
accept the patch over at Selenium because "we write the file dynamically
at build time via XSLT, so it is dynamic and doesn't need dynamic method
generation. And we use that then we don't get pretty api documentation".
Ewwwwwwwwwwwwwwwwwwwww.
--
Ticket URL: <http://code.djangoproject.com/ticket/2867#comment:7>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
