On Tue, Dec 16, 2014 at 5:48 AM, pyramidX <[email protected]> wrote: > I've seen includeme used in some examples of writing pyramid tests, but I'm > still not sure. If the idea is to allow tests to have a lot of the context > of the regular app, then shouldn't I instead move most of the lines from > main to includeme and allow tests to call "config.include('myapp')"? In this > case main would just basically return config.make_wsgi_app() after calling > includeme?
Yep, this is the approach that I take in my apps. The majority of your app's configuration should go into includeme functions as this is a probably the best point of modularity within your pyramid structure. You can include certain features and not include others in tests based on things like this. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
