hi, > Sean, is this along the lines of what you were looking for? > > [1]http://webpy.org/cookbook/testing_with_paste_and_nose > [2]http://webpy.org/cookbook/restful_doctesting_using_request
Yes, this is nice. I know my question was pretty vague, but I was just trying to get an idea of some different ways people do this. I think my problem is really with configuration and not testing, though. Most web.py applications seem to be one off sort of things, designed to be run from the place they're installed. What if I have two or three sites, all running the same code, but using different databases and other configuration? It's tough to separate out the web.py stuff to make the code sufficiently reusable. Where do you get a database connection from, for example? You can't get it from the library since it doesn't know which database to use. It seems like you have to parameterize over the database, but that's a big pain... Anyhow thanks for all the interesting responses! Web.py is awesome! Sean --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
