Am 17.02.2011 04:48 schrieb Michael Pedersen:
I'll admit to being confused still: Which machine is Florent's? Where
does the current www.turbogears.org <http://www.turbogears.org> actually
point?

Ok, that obviously needs clarification: www.turbogears.org is our old server where all of the components (os, python, svn, trac, moinmoin wiki etc.) are outdated now. The server had been granted by Webfaction a long time ago, but actually only as a temporary solution, we're really drawing on their generosity already and promised to move for a long time already. *We really shouldn't touch that server any more*. The plan had been to move to Florent's server but it was never realized since everybody was busy. Later SF came up as an alternative since Mark is working there and since they also use TG2 so we have some connections anyway. But Florent's server is still interesting at least for the CI stuff, and maybe also for bug tracking, at least until SF offers a more viable solution.

    As far as integration/performance tests, what were you thinking?
    Behavior-driven tests, using something like Lettuce or PyCukes?
    Scripted installations?  Something else?

I'm thinking that we should be able to do the following:

    * full unit testing with 100% coverage
    * testing of the installation from scratch (ultimately, on a variety
      of platforms)
    * performance testing (using pystones to benchmark the machine, and
      then using that to normalize the requests/second for a few pages
      out of a quickstarted application)
    * Possibly scripting tests for a few extensions and making sure they
      work properly (such as tgext.admin)

I also thought of writing a more realistic, sophisticated reference TG app that could be used as base for the benchmark and functional tests and also serve as demo app for new users. That would be better than only using a hello world or quickstarted project to test TG performance.

But of course, the tests should also quickstart apps with different options and test these. I.e. we should not only test tg, but also tgdevtools. I think currently tgdevtools has no automated tests.

-- Christoph

--
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" 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/turbogears-trunk?hl=en.

Reply via email to