Thanks again Malcolm. It looks like this is starting to get beyond my comfort level. Given that and my time constraints, it looks like Selenium is a non-starter. I guess I'll just have to rely on humans to do that part of the testing. The Selenium IDE worked fine but unfortunately it's not possible to record results.
Cheers, /Paul On Mar 9, 9:06 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Fri, 2007-03-09 at 12:59 +0000, Paul Childs wrote: > > Thanks for the response Malcom... > > > > Does the same URL work if you aren't using Selenium? I'm trying to trim > > > down the problem to something smaller. > > When I typehttp://127.0.0.1:8000/idms/into the address bar I do not > > get a Django error and the proper page is rendered. > > Then, unfortunately, I have no idea what the problem is, because it's > something introduced by the Selenium process. I'm not a big Selenium > user, so unsure of what it's doing. > > Sounds like you need some way of seeing the URL(s) that Selenium is > requesting from your server so that you can isolate the one that is > causing problems. > > At a very low-level, you might be able to do this using tcpdump or > ethereal or something like that (ethereal/wireshark, even better) -- if > Selenium is talking to the browser over the local network -- and > extracting all the HTTP-type packets to look at the requests. There's > probably an easier way, though, since somebody must have to debug the > Selenium interactions at some point. > > Regards, > Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
