+1 for Jesaja's answer On Friday, December 7, 2012 8:56:05 AM UTC+1, Jesaja Everling wrote: > > I think you should have a look at Selenium. > http://seleniumhq.org/ > It remote-controls real web-browsers, thus you can use it to test > things like the JavaScript "lightboxes" that are displayed in your > application. > There is a Firefox extension called Selenium IDE, which allows you to > record what you do in the browser, and which is a great starting point > for your tests. You can export the recorded tests as Python code. With > just a little work you will have a test that opens your browser, > interacts with it just like you would, and is able to verify that CSS > classes or strings exist in the HTML. I think Selenium is a great tool > for functional tests of websites, and it should allow you to make sure > that the ported application works like the Pylons application did. > > Best Regards, > > Jesaja Everling > > > On Fri, Dec 7, 2012 at 7:57 AM, Marius Gedminas > <[email protected]<javascript:>> > wrote: > > On Thu, Dec 06, 2012 at 04:21:45PM -0800, Mike Orr wrote: > >> I'm porting a Pylons 1 application to Pyramid and I want to write some > >> automated tests. It has only a few screens but it has a large number of > >> input variables that are shared between screens, and it makes numerous > >> calls to a C library (using ctypes) that may return error messages, > which > >> are propagated to the user in a delayed manner similar to flash > messages. > >> > >> Currently I have a pair of rudimentrary Twill scripts to test the new > site > >> and compare it to the old site. But the Twill shell has a lot of > >> limitaitons so I'm thinking of switching to Twill's Python API or > unittest. > >> So I'm wondering if anybody has any suggestions between these or ideas > for > >> how to design the tests in Pyramid. > >> > >> I'm leaning more toward functional tests first because the Pylons code > was > >> already written by someone else, and the client is most interested in > >> whether the site behaves the same as the old site and returns the same > >> results, as opposed to what each individual function does. I should > fill in > >> those low-level tests later but I think I need some more "practical" > tests > >> first. > > ... > >> So, anyone have any ideas? > > > > I like zope.testbrowser for functional tests. AFAIU it's Twill-like > > (I've never used Twill), but you have the full power of Python instead > > of a restricted domain language. > > > > Marius Gedminas > > -- > > The BeOS takes the best features from the major operating systems. It's > got > > the power and flexibility of Unix, the interface and ease of use of the > MacOS, > > and Minesweeper from Windows. > > -- Tyler Riti >
-- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/CUv2MipJGvgJ. 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/pylons-discuss?hl=en.
