Comments on: Running browser in the middle of a Pylons test http://blog.pow.lt/2009/12/01/running-browser-in-the-middle-of-a-pylons-test/ Pow! Wham, bam, kapow! Sat, 27 Feb 2010 21:39:41 +0200 http://wordpress.org/?v=2.8.6 hourly 1 By: Ian Bicking http://blog.pow.lt/2009/12/01/running-browser-in-the-middle-of-a-pylons-test/comment-page-1/#comment-14 Ian Bicking Mon, 07 Dec 2009 03:07:02 +0000 http://blog.pow.lt/?p=83#comment-14 Wait... capture and replay is unnecessary now that I think about it. Wait… capture and replay is unnecessary now that I think about it.

]]> By: Ian Bicking http://blog.pow.lt/2009/12/01/running-browser-in-the-middle-of-a-pylons-test/comment-page-1/#comment-13 Ian Bicking Mon, 07 Dec 2009 03:06:17 +0000 http://blog.pow.lt/?p=83#comment-13 Consider submitting this as a patch (or even better, a fork/pull request): http://bitbucket.org/ianb/webtest/ (I think you can just use self.app for TestApp instead of pylons.test...) You might even have something like a flag in TestApp, on_failure_serve, which would start the app if you get an unexpected 500 response, and then replay until that point. (Well, capturing and replaying would be another feature I guess, but a cool feature, and doable -- though maybe not entirely within TestApp.) Consider submitting this as a patch (or even better, a fork/pull request): http://bitbucket.org/ianb/webtest/ (I think you can just use self.app for TestApp instead of pylons.test…)

You might even have something like a flag in TestApp, on_failure_serve, which would start the app if you get an unexpected 500 response, and then replay until that point. (Well, capturing and replaying would be another feature I guess, but a cool feature, and doable — though maybe not entirely within TestApp.)

]]> By: Marius Gedminas http://blog.pow.lt/2009/12/01/running-browser-in-the-middle-of-a-pylons-test/comment-page-1/#comment-11 Marius Gedminas Tue, 01 Dec 2009 19:08:36 +0000 http://blog.pow.lt/?p=83#comment-11 Nice! Instead of importing urllib2 and relying on it to import urlparse into its namespace, I suggest you import urlparse directly. I'd also suggest moving the hardcoded port number (5001) into a ServingTestApp class attribute, just on general principles. (Also it would let you do things like self.app.testing_port = 5002; self.app.serve() in parallel interactive pdb sessions, if you like that sort of multitasking.) Nice!

Instead of importing urllib2 and relying on it to import urlparse into its namespace, I suggest you import urlparse directly.

I’d also suggest moving the hardcoded port number (5001) into a ServingTestApp class attribute, just on general principles. (Also it would let you do things like self.app.testing_port = 5002; self.app.serve() in parallel interactive pdb sessions, if you like that sort of multitasking.)

]]>