> uhm. How many tests do you want to run in a day ? let's say a test run > takes 20 minutes. You can spin 72 jobs a day. Need more ? Spin another > VM.... days where processing power was limited are gone for good. > >
Are we talking unit-tests or integration-tests? For unit-tests, people doing TDD want interactive-performance. They configure watchers on their files, so the tests run locally each time they save them. It means, their entire test-suite of unit-tests should run in a second-or-two, preferably less. How many times do they expect to run them in a day? I'm not sure that's even a relevant question to ask... (At least not for unit-tests... If it is, it shouldn't be...) As many times as they save their files... Web-apps, specifically, are usually very light on the compute-side - they are mainly I/O-bound, not CPU-bound. I have seen several lectures showing live testing-sessions that run hundreds of tests in less than a second. You can not do this if your unit-tests are using a database. The minutes-scale of tests, should be integration-tests, not unit-tests. These are usually ran somewhere-around 5 times a day per-developer, according to what I've seen. > > uhm2. This is just asking for nightmares. If you want speed (don't want to > involve a database) you test "transformations", not the fetch-transform > couple. > > Sure, but you want to use your existing business-logic core, which usually contains db-object-usage... It's not a nightmare to monkey-patch these objects/calls like that, it's actually a pretty common pattern. > > >> You could theoretically monkey-patch this whole statement in >> it's entirety (or any part of it), so it returns whatever you want (say, a >> pre-made 'rows' instance with 'row'-instances inside) >> The 'mock' library should allow you to do that, wile constraining the >> monkey-patch to a temporary execution-context, and tear-it-off >> automatically at the end of the test (either with a decorator, or a >> context-manager that is provided in the library) >> >> > > Good luck :D > 10x :) http://youtu.be/yFA-FFaEZPo -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
